The state command is intended to NOT make global or permanent user changes, such as setting up registry entries, particularly if you use the “activate” command. Conveniences, like being able to treat a perl script like a command or double-clicking from the desktop, aren’t going to be available, and are going to hobble your ability to switch between Perl versions on the fly.
As a general practice, the file-is-runnable convenience, (which comes from Linux) will limit your options and may not be something you should rely on. Even on Linux, the proliferation of partially incompatible shells over the past decade means that assumptions about the user environment which could be fairly safely predicted in the past are much less likely to be correct now.
Also your use case of making a link from C:\ to your personal AppData folders is problematic because it’s conflicting with the way that Windows manages system-wide exectuables. You should probably investigate using the
state checkout
command instead. That’s intended to give you a permanent, externally accessible, runtime. After using checkout, I would expect that the old way of setting up registry entries manually will still operate on Windows 11.