Arguably yes. I think the big improvement is that an upgrade is really just switching from image A to image B, rather than dozens to hundreds of individual package transactions. Furthermore parts of the system are fully mutable (e.g. /etc) allowing you to run automation against a system post install for more customisation.
... and it works fabulously. I have been running Bluefin (same folks as Bazzite) from one of these templates for about 6 months and it has been a near on flawless experience. I have moved from Fedora 40->41->42 without having to touch a traditional "upgrade".
Fair call. In any case I think you'll find things moving towards bootc and away from having to know rpm-ostree at all. The bootc documentation for fedora is pretty good and the Universal Blue project has built some awesome distros that use bootc.
... And we all know that rolling upgrades frequently introduce breaking changes that don't make sense for enterprise environments. To your (great) point: Customers pay companies like red hat for software stability, both in how it works and how their software interfaces to it.
Is the problem ultimately to do with your configurations on your centos 7 boxes? Converting to rhel should be easy if you aren't doing anything that red hat wouldn't support in rhel.
We all know it's just made up stuff to feed the narrative of evil IBM making RH evil. Not even the plausible scenario of IBM changing the source code licencing of hashicorp software back to something genuinely open can change people's minds.