This report is a bit confusing, so need some information.
On the system where you received this error, please try running any of the commands from Microsoft.PowerShell.Utility, such as get-member, or get-date. The error message and the information you provided seems to indicate that the module is already loaded, so we are looking for other indications that it is not.

I hear you. We just have to be very thoughtful about what we bring into the rest of PowerShell based on the amount that users will leverage it. Part of the reason that we did PowerShellGet is to allow you to bring in everything that you want, no matter how large or small. :)

My apologies, Joel. Was doing multiple things at the same time, and I only tried the -UseBasicParsing case which worked instantly. You’re right, I’m seeing the same thing without it. I’m filing something internally.

WMF is generally tracked as closely as possible to Current Branch Windows 10, so I'd imagine that this fix would be delivered as part of that. WMF 5.0 will be supported for 4 months after 5.1, but only for critical security issues.