You should be able to get this with either the REST API directly, or the cmdlets build into PowerCLI. From there, you can build your day 2 action as XaaS using a scriptable task with the REST plug-in to fetch the vROps ID based on the vCAC and VM entity ID.
This should work via the HTTP-REST pack in vRO? I'm thinking of using that for getting vRO/vRA to talk to vROps and grab that VM object-id, based on the VM's name, and then generate the link for the user to receive via email. All this should be accomplised by a XaaS item or day 2 vRA action.
Yeah, I can't think of why it wouldn't work.