The point wasn’t so much that there are no replacements, more that every script and every shortcut and everything else using them will have to be changed to work with the Wayland alternative.
A switch from X11 to Wayland is not just a minor change to your workflow though unless you used all defaults before.
It requires you to replace your window manager, all the little tools related to things like clipboard, automation, screen locking,…
And you would have to do pretty much all of that up front to be able to use Wayland long enough to know if it even works on a permanent basis for you. That is a lot of work to put into a project that has a sketchy history of people claiming for nearly a decade now that it works just fine for everything while clearly not working fine for all use cases.
I would say that is a false dichotomy. Almost everyone agrees that X11 isn’t the future but the support for Wayland and the specific ways it does things, is not nearly as universal as that. It is just that the problem is huge and has already taken 15 years or so and so it looks like if we want some alternative to X11 that will be done any time soon Wayland is unfortunately the only game in town, no matter how flawed it is.
Counterpoint, if all of the people advocating for wayland actually worked on improving wayland to a usable state instead maybe people would actually want to use it.
If anything, we can expect more people making Wayland compositors as hobby projects, if Waylands claims about a simpler codebase are to be believed.
They are not. Wayland compositors have to do a lot more of the same thing in every compositor than window managers ever had to. So many in fact that their whole central design idea has to be corrected for by everyone using wlroots to implement those common parts to get anywhere anyway which means wayland compositors in other languages without wlroots bindings are less likely.
I think Borg Backup would fit your needs. You would still need to reinstall things like a boot sector and recreated partitions but on the other hand file based backups have the advantage that you can restore individual files when needed too and that it is easier to only backup what changed. Just make sure to exclude any temporary files you don’t want to keep from the backup (e.g. cache dirs, log files that get rewritten often and aren’t relevant long-term,…).
It also means booting is untested until something like a hardware fault or a power outage forces it onto you and you have to deal with any reboot issues at the worst possible time and a time you did not choose.
Only in the licensing space in particular there is really no good reason to hide the exact rules what is acceptable and what isn’t. Nobody is going to circumvent your defences if they know exactly which licenses you allow.