Is resxtop on vMA ever going to be either fixed or adequate workaround provided?

I used to make use of the vMA more during the pre 5.1 days to avoid having to enable SSH on all of my hosts and to have a central point of host management for CLI type stuff.  Version 5.1 broke resxtop in the vCLI as has been documented and discussed in the past, and I abandoned the vMA as a management platform, since resxtop was a large part of what I wanted to use vMA/vCLI for.  I wound up enabling SSH on my hosts every time I wanted to look at performance.  I was hopeful that the 5.5 version would have a usable resxtop, but alas, it still is completely unusable!  Still a "known issue" listed in the release notes:

• resxtop fails to run agains vSphere targets
  When you run resxtop against a vSphere 5.5 target, an error results.Workaround: If your environment supports this, run esxtop in the ESXi Shell. Otherwise, no workaround.
  • If the SSL certificate is set in the vCLI client, the following error results:
    SSL Exception: Verification parameters
  • If the SSL certificate is not set, the following error results:
    Login failed, reason: HTTPS_CA_FILE or HTTPS_CA_DIR not set

• No output when running the resxtop vCLI command.
  When you install vCLI on a Linux system and attempt to run the resxtop command, no output results.Workaround: No workaround. You might be able to run the esxtop command in the ESXi Shell if you have access to the system. Enable the shell before you run the command.

Is this ever going to be fixed?  It has been broken for 2 years!  Or has anyone figured out a workaround?