I have also tried both and I agree that Intel XDK at this stage seems buggier and messier than CocoonJS (but there are bugs in CocoonJS as well). Let's hope Intel sorts it out soon. Intel XDK is free to use while CocoonJS will cost money.
Another option to consider is gameclosure. While CocoonJS and Intel XDK support both webview and canvas acceleration, gameclosure is only about canvas acceleration, but seems very good. I'm not sure Construct2 supports exporting the combination of webview and canvas, so it probably doesn't matter in many cases.