Hyper-V 'Sources WMI vs. Batchscript

Almost all Windows-based monitoring using WMI, that is what Microsoft provided as the primary method of remote monitoring/information collection, so it's not a surprise. If you worry about using too many ports, perhaps you should lower the number of threads you are using? I think it's wmi.stage.threadpool.maxsize  in the sbproxy.conf. I have not played with this option myself.

https://www.logicmonitor.com/support/collectors/collector-overview/collector-capacity/

I expect that writing a custom BatchScript for WMI calls would only help if the WMI Datasource has lots of instances AND you can collect the same data in fewer calls. You also need to balance supporting custom coding for your org vs built-in functionality.