Static DCHP Address-Binding on Hyper-V Private vSwitches?

Recently got a new laptop with Windows 10 Pro. Prior to this, always used VirtualBox for locally-hosting VMs to do my development work on. Opted to try out Hyper-V since it's also free (and hopefully requires less-frequent reboots for hypervisor-driver updates).

Initially, I set up my VMs to use an external vSwitch. However, external vSwitches require putting my wifi interface into bridge-mode. When in bridge mode, network performance goes in the trash - for both my VMs and my host: using various speed-testing tools, my connection-performance drops from 500Mbps-bidirectional to about 4Mbps down/200Kbps up.

As a workaround, I switched to using private vSwitches and using connection sharing. This restored my host's connection-performance to their initial levels and sped my VMs' networking up to nearly the same speed, as well. Unfortunately, the cost seems to be that my VMs' IP addresses change regularly. Worse, if I go into the VMs and change to static IP addressing, the private vSwitch's gateway refuses to route.

So, the question is, "how do I provide persistent address-binding to my Hyper-V VMs without trashing my networking-performance"? I've seen various posts about using external interfaces and changing driver-settings to disable the broken "optimization" settings associated with bridge-mode, but, those settings don't seem to be available when the base NIC is WiFi.