Those scenes take a moment to load because our own code discards them when you're not looking at them... to save memory! It's nothing to do with Chrome. And if you have a bunch of other tabs open using memory, I don't see how that has anything to do with Construct. If you have them open while you work, then even if we made a native app, presumably you'd still have those other tabs open?
Whenever anyone says "I don't like using Construct in the browser" I always ask these questions to try to figure out what the real problem is, since if there is some real problem, we can try to fix it. But I can never seem to work out what any real problem might be. Which is part of the reason I still think it's absolutely fine - in fact great - to have browser-based software.