Not with the QSP interface. The player can put the different sections (Objects, Actions, Additional Descriptions, Preview etc etc ) of the display wherever they want and at what size they want. The player can even decide what amount of information is actually displayed inside those sections too. Sure the developer ultimately decides what goes in to what section, but insofar as the sections in Girl Life are currently constituted the contents of the named sections make sense.
I reference Girl Life as it's certainly the most user friendly of the QSP games i've played, the dev's have given the player the choice to display an absolutely huge amount of background info if they so choose and because they've chosen to not use Awesomium_process the interface isn't locked by the dev at all.
So basically you can resize a subwindow, big deal. In a properly designed interface that shouldn't be necessary. As for displaying varying amounts of information again that goes back to the dev. Typically that sort of option is referenced as verbose level, useful to have different levels in logging situations but in a game if you can't find the right level for 99.99999999999999% of potential players you're just a bad dev.
I notice you didn't say anything about screen management. I haven't worked with RenPy in about a year but I do do Python coding almost every day at work (Senior Linux Systems Engineer). A lot of styling, tables, borders, etc can be easily laid out in HTML/CSS and changed on the fly. Also 99% of QSP games (and even RenPy games here on F95) have minimal if no audio at all,so that's a moot point. QSP also uses AVCodec (fmpeg fork) for it's video player which can be easily updated.
Any game with a heavy UI base you're gonna work 10x harder on in RenPy due to the fact button templates, border templates, window templates, icon templates *insert any image template here* is going to have to be hand crafted in your favorite image editor of choice, then you have to manually place them (to the pixel) on each screen. 90% of that you can do in CSS with a few lines of code and Div's to auto place the majority of your content.
RenPy is great for your standard run-of-the-mill VN game, because obviously that's what it was made for. Anything else you're going to have a rough time just because RenPy wasn't made for UI/Video heavy based games. But as they say, to each their own.
Also who the hell cares about security? lol. If anything, you can make something extremely insecure that phones home to a server, places random malware, and even execute shell code straight from the python interpreter. QSP you're gonna be hard pressed to do that.
As far as screen management goes they've virtually the same. They both use the same basic property set and include the option to define styles (CSS classes) to be used on multiple objects by reference. Admittedly you can float shit easier in html/CSS but given the frankly amateurish interfaces common to most indie projects let alone QSP titles, which offer about as much visual complexity as twine or rags, you might as well just do them as pure html and save people the time getting a player.
Just cause few choose to use it among the low end patreon amateur dev community doesn't make it moot, it's still a capability that QSP does not have. Look at the larger paid projects like those you'll find on stream and they tend to be used more.
AVCodec is x264, like I said VP9 is x265 equivalent so better quality to size ratio available in RenPy. The fact remains the RenPy devs intended the use of video or they wouldn't have given the option while it took the QSP fan community to bring that support to the platform cause the original dev felt it unnecessary, undesirable, or was just too damn lazy.
As far as security goes anything you can make a browser do you can make QSP do because that's basically what a QSP player is, a halfassed web browser with no security of any kind. Now you do make a point that you can put raw python into RenPy scripts but given RenPy uses it's own proprietary script set which is compiled by their code at runtime the platform can ensure a certainly level of protection against untoward actions.
Anyway RenPy was made to support anything those who use it might want including a complete graphical interface with all the bells and whistles, music, sound FX, voice acting, videos, frame based animations without having to resort to crappy animated gifs, etc... while QSP was designed for those who wanted effectively iframes they could resize and rearrange.