Conveniently, given that any Flash content published as SWF was probably authored at least 10 years ago, you could very likely get away with using such an older version of Flash to view such sites.
Rather than tracking one down yourself, I'd suggest, for best compatibility, just using a VM of an OS that ships with an older version of Flash. For example, later releases of Windows XP.
That's what the blog One Terabyte of Kilobyte Age (https://oneterabyteofkilobyteage.tumblr.com/) uses to generate its screenshots, and they almost always work.
FWIW, Ruffle appears to be able to play Flash content within a web browser: https://ruffle.rs/demo/
(Related Internet Archive post on their new Flash collection: https://blog.archive.org/2020/11/22/flash-back-further-thoug...)
Like breaking TLS cert validity date checks.
Though, I suppose if some website hasn't migrated off Flash by 2020, it's probably reasonably likely to also be in the subset of websites that haven't implements https by now as well...
I'm wondering if the IT team which produced that pice of software is gone since years.
Edit: I somehow missed that my spell checker replaced "have facepalmed" with "gave poisoned"...
The copyright stance on breaking DMCA for preservation is far more clear when the original owner is explicitly dropping support.
I don't think I like that. Yes, using Flash in a web browser once it has stopped receiving security updates is a bad idea, but what if you need to view a website in the Wayback Machine which incorporates flash, and you've set up an isolated VM for the purpose? I suppose you could set the VM's clock back, but that's a major PITA which could potentially cause other issues.
The existence of Flash Projector softens the blow significantly, but there will be some content that must be viewed within a web browser. Perhaps an earlier version of Flash Player lacks the kill switch?