The problem with running the TIM in any virtual environment is always:
1. Performance (Virtualization removes actual performance from the TIM)
2. The network interface has to be put into promiscuous mode (the one the TIM uses to receive TAP/SPAN data).
Even though it would probably be technically possible to run the TIM in a hyperV environment, it would require the TAP/SPAN Network interface to be put into promiscuous mode. If that works in a HyperV environment, I can't tell.
From my side - I never tried it. I tested it on ESX VM's, VMWare and Virtualbox without a problem.
Docker also works, openshift while providing the TIM Container root-access rights (Which any decent admin will refuse doing).
I would be interested if you manage to get it to run cleanly.
Note that running TIM on a HyperV is not supported by CA. So you are on your own here.