To give some context, I am focused on PC game development, i.e. NWJS export, for relatively large scale tile based strategy games, think along the lines of the old Heroes of Might and Magic games, not so large that it should need to use chunks etc. I can appreciate that maybe this wouldn't make me a typical Construct user,
Hi simstratic great post. I also consider myself as someone in this same category (small game PC indie development). I'm not sure I am Construct's typical user either. And while I have used Unity to a fair amount of success I always come back to Construct for its speedy development...or at the very least prototyping. Truly the biggest limitation I feel is the platform deployment options, and there are many reasons why deployment is what it is, which may include some of the issues you mention (certain memory management/varying degrees of control, HTML5 etc..).
I know people have had minimal full life-cycle success with Construct (on PC/Steam) and the engine is definitely an outlier. And maybe I'm not qualified to say this, but I always feel Construct is one or two builds away from all of sudden being an industry standard. Of course I've been saying this since 2015-- but I definitely think there is something special about Construct. The PC solodev-to-Steam/Other, is definitely not Scirra's main demographic - that said, they have tried to keep those users/features in mind for updates (meaning they are not ignored).
You should research (maybe you already have) some of the more professional, large-game, Construct releases. There should be a list in a thread somewhere - some titles: The Next Penelope, Airscape, Klang, Super Ubie Island - I know there's more. If you were to contact these devs they might be able to tell you if there are any real deal-breakers (in terms of full-cycle, large game development). I know you weren't asking for this, but I guess my point is, most of the time there are work-arounds but there's always things (depending on the game you are trying to make) that would be deal-breakers or just not viable no matter the engine. You just have to figure out what is "acceptable" for yourself, and since everyone has their own "needs", it's hard for Scirra to fulfill everyone's wish.
But it's great you are putting this out there, because I believe with more communication like this helps Scirra know what their users want.
EDIT: when I say if "you" were to contact those devs, I mean the global "you", I know you aren't looking at ask what is possible in Construct.