The Security Update sets all instances and user gameplay to use EAC. While this helps users who do not like using mods, this does not help users who do like using mods.
To solve this, there should an option to create non-EAC world instances.
This benefits players who do not use mods and who want to be protected from them because, by default, EAC will be required for them and for all instances.
This benefits players who are willing to accept the risks of mods because they have the option to turn off EAC and knowingly expose themselves to third-party code. By default, non-EAC instances would be hidden, this is similar to how Labs worlds are hidden. Portals to non-EAC instances should not be accessible to users who have not chosen to disable EAC. Players who have chosen to disable EAC but who are in an EAC instance cannot use mods because EAC is enforced. This ensures that players who are in an instance with EAC by default are not exposed to mods.
This solution needs to be implemented to promote the security of VRChat as described in the Security Update, and to support the dedicated community members who have been supporting VRChat for years and dedicating their time and effort to the improvement and freedom of the platform.