Oh, and they knowingly shipped a broken and insecure Wireguard to their customers, and tried to use their FreeBSD commit status to force it upstream
No, here's an even simpler task: try compiling packages for pfSense.
The clowns from Netgate made it unbelievably difficult, for no good reason other than being antagonist to the open source community.
This is all very ironic because that kind of attitude was the main drive for many to move away from pfsense.
Well, it works.
But try to add some custom parameters to a daemon, which aren't listed on the page. Or try to run more routers than one. Or diag network states even on 4k monitor.
There are a thousands cuts using OPNsense in anything more than a home router. Despite ten years of trying this year I ripped it off where it was installed and replaced back with pfSense.
I'm a former pfSense user that reluctantly moved to OPNsense a handful of years ago after a lot of bad press around Netgate started circulating widely causing me to believe that support for the community offering might wane over time. I was under the impression that many people had moved off of pfSense for home use. I'm surprised by your assertion that it "remains dominant" for free users, and I wonder how you might know this?
OPNsense has been rock solid for me, btw. I was reluctant to switch only because of the time sink and perceived risk. Nobody wants to spend a weekend debugging VLAN tagging on their WAN port or some such. Luckily for me, there were no such issues when switching over.