The IO::Socket::SSL update really shook things up and the modules that depend on it don't have the fall through options to modify the underlying ssl_opts built in. It's a bit of a mess 
To be fair, it's not really a VMware SDK issue, but I do think some enhancements could be added to support it better. It's a legitimate concern to stress the issue of blindly trusting certificates.
I suppose the proper solution would be to write a utility script to accept and build a certificate store that can be access with the CA ENV options that IO::Socket::SSL wants instead of SSL_verify_none.