Yes, that's how NetScan works: it launches a separate instance of PowerShell for every IP address and captures it output. Unfortunately as PowerShell is written in .NET we can't interface with it directly. You may want to decrease the number of parallel threads in NetScan if that slows things down.