Map Loopback Addresses other than 127.0.0.1 between Windows and WSL VM

**Is your feature request related to a problem? Please describe.**
I am developing a local Kubernetes environment using minikube that exposes a variety of ports to simulate our production Kubernetes environment. I want to be able to bind to an address other than 127.0.0.1 for minikube tunnel so that ports like 80 and 443 are not bound on the primary loopback address and still be able to access the loopback address from within WSL.

**Describe the solution you'd like**
Loopback addresses other than 127.0.0.1 such as 127.0.0.2 or 127.10.0.1 are mapped between Windows and WSL. This is the same request as #4349 which was closed but not resolved.

**Describe alternatives you've considered**
Not using WSL.

**Additional context**
n/a

Start by reviewing this issue and the referenced #4349 discussion, then trace how WSL currently maps loopback addresses between Windows and the VM. Done means addresses such as 127.0.0.2 and 127.10.0.1 are reachable across that boundary while preserving the requested minikube use case; the payload names no files or tests.

Written by the indexing model from the issue text.