That's definitely frustrating! To know that your game should be able to run much faster but because of certain programming "restrictions" in place, it is not able to take full advantage of it. One thing that does look bad is, if google was serious about improving html5, this issue would have been resolved quite some time ago. Perhaps they really aren't that interested in going that way. If that's the case, and with Chrome being the benchmark of browsers, our hopes might really rely on the MicroSoft Edge. It's still some way off from being stable or the "it" browser, but maybe this is a good thing for us. Since they need to play catch up, they will have to look at areas that give them an advantage over Chrome, hopefully this is one aspect they might concentrate on. Not sure if there's anything Intel is able to do about this on their part.
But that's the problem nowadays with any technology that is not direct or native (not criticizing Scirra here), cause all the rest will have to depend on so many other groups to be able to function efficiently. It is worth a shot trying to bring this to Google's attention, not sure if they will take this seriously, but at this point, it is the only thing we can do besides waiting.