> 2) Have it manifest itself as a broken symlink to the URL target
This sounds like a good approximation. The target of the symlink could be formatted so that it shows what it is about. In your case this could be
C:\Windows\System32\SystemUWPLauncher.exe(Microsoft.MicrosoftEdge_8wekyb3d8bbwe, Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge)
and this should be understandable as meaning to start the launcher with two arguments. I prefer not to translate the "\"s to make clear the link cannot be used on Linux. This is not an URL, and I have no idea of what the URL used by Windows 10 looks like (and it probably contains an authentication token).
At first glance, this is possible with your current ntfs-3g version (a few days needed to implement).
> Practically, what would the EREMOTE plugin you proposed do?
If you did "cat the-reparse-file", you would get "Error : The object is remote", with consequences depending on the context (typically shell or application aborted).
> 2) Have it manifest itself as a broken symlink to the URL target
This sounds like a good approximation. The target of the symlink could be formatted so that it shows what it is about. In your case this could be System32\ SystemUWPLaunch er.exe( Microsoft. MicrosoftEdge_ 8wekyb3d8bbwe, Microsoft. MicrosoftEdge_ 8wekyb3d8bbwe! MicrosoftEdge)
C:\Windows\
and this should be understandable as meaning to start the launcher with two arguments. I prefer not to translate the "\"s to make clear the link cannot be used on Linux. This is not an URL, and I have no idea of what the URL used by Windows 10 looks like (and it probably contains an authentication token).
At first glance, this is possible with your current ntfs-3g version (a few days needed to implement).
> Practically, what would the EREMOTE plugin you proposed do?
If you did "cat the-reparse-file", you would get "Error : The object is remote", with consequences depending on the context (typically shell or application aborted).