Page Editor: On 'Blank' Pages With Custom Wrappers, Widgets Retain Community Theme Styling

Background: I read recently about how Pages would be managed differently in V5 (specifically, that the 'content' tab would be dropped in the AdminCP Page Editor and replaced with the frontend Page Editor) so am playing around with a test instance on localhost to see how I can convert my existing custom Pages on my V4 community.

I have an "archive" folder on my community, which I use to host restored (or rather, 'recreate') content and old site designs of my website (which has been going for 25 years now... so there's a lot of designs to stage). Because these old designs were made in pure HTML (and many not on Invision Community) the main benefit of V4's Page Editor is that I can efficiently recreate old-school designs and content by creating 'blank' pages and just building out code in the content tab without requiring any of Invision Community's features, functionality or design.

To that end, I believe that any other community admin that creates a new Page choosing to use a completely custom wrapper would also expect the same experience - a completely blank page upon which to build HTML/PHP/CSS/whatever from scratch. Almost as if Invision Community doesn't exist when browsing those specific pages (although it's nice that we can use IPS code and call up IPS features if we do actually need them).

So to basically do in V5 what I've been doing in V4, the idea (if I've got it right - please correct me if there's a better way of doing it) is to create the page in AdminCP, select the appropriate custom wrapper, launch the Page Editor from AdminCP and then place a "Raw HTML" block/widget, then enter my page's HTML/PHP/whatever there.

All's going well on that front, except one issue. The 'Raw HTML' widget, when used on a customWrapper'd blank Page, outputs in a container that adopts CSS styles from the '.ipsWidget' class in my main community's theme CSS. Here's a quick snapshot to illustrate what I mean (ignore the lack of any assets in there, it's a quick and dirty experiment job but imagine there's supposed to be header images and custom background image there somewhere - the point is the container box where the red circles mark the corners of)

That widget border shouldn't exist, and that light grey-ish background colour shouldn't be present either. It should just be transparent/showing the white background behind it. Now that I take another look at it, that "Lorem ipsum" text at the bottom of this snapshot should also be coloured in the default black (rather than navy/blue, which is the same colour as my current V5 community's default theme text colour).

I know that technically the Raw HTML widget is a widget, so logically it follows that it would use a container wrapper that matches with my main community apps' frontend, but the objective of creating custom pages with custom wrappers is to have a completely blank or 'clean' experience. So I feel that keeping this styling betrays that use case, which makes me believe it's a bug/oversight (which is why I'm reporting it here).

It's a small issue I imagine, and I could probably get around this by adding CSS in my CSS template files that overwrite the .ipsWidget values, but that's additional busywork on potentially hundreds of pages (and 10+ css templates) that I don't need and shouldn't have to deal with. Is there a way to make sure that widget containers are stripped of their CSS values whenever an admin creates a Page with a custom wrapper assigned to it?