In a conversation I had with VMware, I was advised that the KB article that was linked in my prior post should be updated as it develops. They also suggested subscribing via RSS to have additional visibility.
Unfortunately, that also means that there haven't been any developments, as the article doesn't show to be updated since 17 Feb.
If performing /etc/init.d/wsman restart from your ESXi host (via support mode/console) allows you to successfully connect to OMSA and successfully discover/inventory in OME, the work around provided in my prior post should work for you, as it will automatically restart WSMAN without intervention once completed.
Also, as a side note, if you aren't wanting to reboot your ESXi host, but want the benefits of wsman being restarted automatically, once you make the edits, just perform the same commands that will be performed at boot while it's running (kill cron, echo the line to the crontab file, restart cron), and you'll be all set, with the initial edits and auto-backup ensuring that this will persist through reboots.