Also, keep in mind that these identical entries with "" suffix are directly from Perfmon, we are not adding these suffixes. So, there is another object in the performance metrics manager on this machine. It could be cloned VM, maybe a replica. And I would agree with Alec that reboot should fix the issue.
Also, I've checked with support team, they recall the following conclusion for one similar case (which is unfortunate but by design of hyper-V):
"We suspect that issue might occurs by Hyper-V design, if dedicated resources for that machine run on multiple NUMA nodes."