I think the chrome audio issue was a sort of honest mistake from scirra (using a beta feature of chrome in a good chunck of versions), but even then I still think relying on chromium devellopers not breaking things is an issue.
You have to count the good in with the bad, though. Yes the proprietary chrome audio api was an issue, but many other things were not (such as webGL, which eventually got adopted in IE and Android).
Also WebRTC was implemented right on time, if scirra had chosen to implement multiplayer early, with the first draft of websockets (which included UDP) or DataChannels, we'd have a problem today, but fortunately Ashley chose wisely.
With node webkit [...] Crosswalk [...] cocoonJS [...] awesomium
Yeah, wrappers have dropped the ball recently. CocoonJS appears to be the only game-oriented wrapper, I think webkit is geared towards application developers, otherwise they'd cut many unnecessary things to reduce the overhead.
Intel apparently worked out better, though.
you should be able to convert them on your side
You are able to convert c2 projects to work with many wrappers, but it's a bit of a pain. Many users have done so in the past. Construct's exporters just abstract away the conversion process.
we are adding yet another third party over that,
I absolutely get (and agree with) what you're saying, but keep in mind the intention is never to leave those wrappers permanently. Ashley is intent on cutting every proprietary or third-party tech possible (jQuery used to be a c2 dependency).
The problem is that, outside the browser, our options suck. The sudden appearance of HTML5 exporters on competitors (MMF, GM, Unity, etc) won't change much, since those competitors have their own native exporters as well, which in turn tends to make HTML5 a second-class citizen.
We all know the solution: make a first-party native exporter. But as Ashley stated multiple times before, that's not going to happen: maintaining multiple codebases is exponentially more difficult, and will slow down development a lot (and fast iterations are one of the major selling points! I don't think there's a single person in the forums unhappy with the pace of development at Scirra). If we had a bigger userbase, a commercial exporter could be viable - the XML format is pretty easy to work with, even if it has its issues - although past actions by Scirra have shown they don't exactly welcome this approach. Keep in mind a native exporter would break all plugins, requiring them to be written in said exporter's language (a garbage requirement IMHO).
Personally, I'd like to see development move in the opposite direction: move the editor itself from C# to HTML5, so we could extend it a bit more easily. The same arguments apply in support of my thinking: less dependency on third parties, less vendor lock-in, multiplatform support, better consistency between edittime and runtime. Note that I'm not talking about a browser-IDE or cloud-editor like Impactjs' Weltmeister, but a full-on desktop javascript-based application such as Brackets.