Any build system producing a webview app will likely perform identically. The build systems are just different ways of producing the same result. Since it's the browser engine powering the webview that determines runtime performance, and there is nothing different about that, it's likely the same. The only exceptions are if you change the webview (e.g. UIWebView/WKWebView, but all build systems now support WKWebView).
Canvas+ on the other hand is not a real browser engine, and not officially supported. We dropped support for it a long time ago because it had loads of problems. It is missing tons of features and had basic problems like being unable to manage memory so even medium-sized games crashed. For a small number of people their games could navigate these problems and more or less by luck they kept working, and they wonder why we don't support it, but it's totally a no-brainer from our point of view - it's not worth supporting at all.
Also, even if it's faster, in my opinion that doesn't matter. With Construct Classic we learned an important lesson: slower and working is better than faster and broken. We did loads of crazy optimisations for another 5% speedup and it got so complex and difficult with all these internal performance hacks that it just totally broke some games. Someone whose game runs 10% faster is a bit happier, but someone whose game does not work at all is extremely unhappy. So making something that works robustly is more important, even if it's not as fast as possible. So basically in my opinion it doesn't matter if Canvas+ is faster: it's so badly broken it doesn't matter.