I think there was a missunderstanding here:
Scott was trying to illustrate that there is no such tool to show the mapping of vCPU to pCPU at runtime. (IE: which pCPU core is running which  vCPU thread) Because, as he correctly said the CPU scheduler changes at a really fast rate so it wouldn't be possible to keep track of. 

If what you want is to have a vCPU to pCPU operprovision (how much vCPUs am I using/can I use related to the pCPU's I have available) you can do it from some vROPs dashboards. 

Hope I have clarified the situation.