This can affect any Powershell Automation Scripts you have running that will be waiting for user intervention! You can change the Nutanix Connection method to Force the Connection using the following syntax:
Connect-NTNXCluster -Server "Your server here" -UserName "Your user" -Password "Your password" -AcceptInvalidSSLCerts -ForcedConnection
Note: It is the ForcedConnection that enables the bypass of the mismatch for your scripts.
Hopefully they will update the Version with the next iteration of the Cmdlets without the apparent typo of 5.1.1 instead of 5.11.
Please feel free to "Like" to mark as "Best Answer"
Kind Regards
Andy