The defenses used here are equally valid if Construct 2 was a tool using Adobe Flash "Everything is a third party software!"
However, in regards to a screen recording issue, it is a known issue that Chromium and NW.JS create many instances to run a single page (which is hidden by NW.JS as a "native app" through wrapper). This is an issue inherent in the specific choices of HTML5 and its wrapping options based on Chromium.
If Flash was chosen as the basis of Construct 2 would there really be such an accepting response to "But it's not my fault the browsers are all killing Flash!" ???
Native has, is, and will continue to be a standard of all platforms, because you need native to run the emulators/interpreters/browsers/Flash plugins.
The design phrase "Less is more" was never more clear than when I look at the "many options" I have to export my C2 games to and none of them work for my entire customer base on Steam, let alone the other platforms our game was planned to come out for.
So yes, the fact that so many screen recorders don't work with Construct 2 NW.JS exports is an issue that Scirra must be concerned with in some form.
Scirra may be unable to fix it themselves at all, but to be concerned and using its large(r) industry standing/PR power and fanbase as leverage to apply pressure to the NW.JS staff to apply pressure to Chromium developers (officially as a company, not just "C2 users individually requesting"), is what Scirra's paying customers would expect from the developer of the product they purchased. If Unity or Unreal Engine 4 was doing half the things Construct 2 is doing to me you can bet I would be in their forums complaining too.
Edit: Also any NW.JS verison from the "most stable" 0.10.x to the newer post-NodeWebkit-rename are equally wreaking havoc on my game in different ways. Not a viable solution, especially when Steam Greenworks breaks in some way at every change too.