In this case, there are two reasons IMO for not doing this:

1. Backward compatibility might be affected.
2. It may be more important to conform to venv conventions than Powershell conventions in this specific case.

I wasn't aware that PowerShell scripts out in the wild follow these namig conventions rigidly - that hasn't been my experience. Is it the case? Who polices that? Of course, in environments that mandate this level of conformance, you can easily subclass and override the relevant functionality to have the script be named exactly how you want.