>>105964951
Given what the update does is quite simple, I don't think it will fuck up something during the installation, and just after that. Some anon here reported success adding this package some generals ago, with the system properties showing 22H2.

Theoretically, since your W10 version will now be 22H2, you might be limited to 22H2-destined updates.
But as every W10 version from 2004 to 22H2 is Vibranium-based (the system files are still internally versioned 10.0.19041.xxx: 19041 being the initial release of Vibranium - version 2004), there shouldn't be any potential issues, at least until October this year when non-ESU support for mainstream Windows 10 22H2 systems ends.
>one scenario that comes to my mind is a possible splitting of Vibranium updates between LTSC 2021 and ESU-only 22H2, the latter of checks whether your system is licensed for ESU before installing the updates
>ESU, for obvious reasons, does not handle [IoT]EnterpriseS due to the edition's long-term-service nature - supported at most until 2032
>although MAS' TSForge did claim to support activating ESU for IoTEnterpriseS before release 3.1

It will depend on whether the CBS packages within any further LTSC 2021 and ESU-only 22H2 updates continue to be identical like how it currently is, from that date. If the status quo doesn't change (and Windows Update will still deliver LTSC-specific updates for unofficial [IoT]EnterpriseS 22H2 systems after that date, without sacrificing 22H2-specific code and features on that side), you're free to go.
Yet again, time will tell. You can always uninstall the enablement package like the paste says to revert back to 21H2.
>unless you rebased the component store (WinSxS) after installing this, in which case you baked them into the installation