Looks like you want to make a point that is not really a point.
At least not for me.
The title of your thread is incorrect, the conflicting cmdlets (with Hyper-V) have been there since 2011.
I personally prefer to be warned of potential conflicts, instead of discovering them on the go.
But I agree, that is a personal choice. To each his own.
The Hyper-V module was included for the first time in Windows 2008 R2 in 2011.
Since PowerCLI, and the Get-VM cmdlet, officially saw the light in 2008, your logic should direct you to talk with Microsoft.
Since PowerShell is open, you can easily create an Issue on the PowerShell repo for that.
When multiple companies produce PowerShell modules, and since there is a limited set of approved verbs, it seems unavoidable that conflicts will arise.
Luckily the PowerShell Team foresaw this, and provided some workarounds (see my earlier reply).
The MSI you seem to like is only usable in a Windows environment.
The introduction of the PowerShell Gallery, made distribution of modules portable.
Which was a requirement to allow PowerShell v6 to go multi-platform.
If you want to stick with a MSI, there are tools and procedures to package modules in an MSI file.
See for example From script to server – Deploying solutions with PrimalScript 2014 (Part 2)