They work GREAT on the new 14.0.0. It’s other system modules under the contents directory that cause issues…the easy way to get past it is to rename your contents directory to contents.bak and get booted up successfully and THEN copy over your numbered sys-modules from contents.bak to a new contents directory in small batches, rebooting in between batches, to see if there are any breaking changes. Some are well known (like themes or mission control this round) so just leave those in the contents.bak until you get all your other well behaved sys-modules migrated. Some broken modules will be quickly fixed by the dev team and you can reinstall them once they are released again. Others may be broken forever.
Bottom Line: changes to HOS that break sys-modules are not atmosphere’s fault. Easiest way to prove that your atmosphere installation is good is to take sys-modules out of the equation while you upgrade.