I will take another stab at what has been raised shortly

As mentioned in #27037, the name of the parameter -Current is not obvious and not very discoverable. I'd like the name to be more obvious, such as -CurrentPowerShellProcess. If we have to, we could then use ``-current` as an alternative name for this parameter.

@doctordns - the parameter Current is for most people going to be self explanitory as you are clearly looking to get the Current Process surfacing & using the PowerShell Engine.

There isn't any real need to expand this to CurrentPowerShellProcess and also as PowerShell can be embedded in a C# application calling this would then return that applications process as there is no real PowerShell process to return.

So it doesn't actually make sense to call it as such.

The @PowerShell/wg-powershell-cmdlets discussed this. Since $PID is explicitly not allowed in RestrictedLanguage mode. We are concerned if this would be a workaround to a deliberately intended design. We ask the Security WG to review. Otherwise, we don't have concerns about Get-Process -Current

On further review prior to Engine WG discussing #26950 & also based on @SteveL-MSFT comment above I think that to please the Security WG would be best for if Get-Process -Current is run in a RestrictedLanguage mode that this should return an Unsupported in this Language Mode error to the caller.

As such there will be more work to do in this PR to achieve this.