WSL2 does not work with GlobalProtect on localhost

Nobody has claimed this yet.

ssue:
We’re facing an issue with WSL2 where traffic from WSL is unable to route to Prisma when GlobalProtect (GP) is running on the host Windows machine with an Explicit Proxy enabled on Localhost 127.0.0.1:9999.

Environment Setup:
GlobalProtect VPN enabled with Explicit Proxy
Proxy PAC listening on 127.0.0.1:9999
WSL2 traffic appears to use the Windows Hyper-V loopback interface

Question :
How can we configure WSL2 traffic to route through the GlobalProtect Explicit Proxy running on the Windows host at 127.0.0.1:9999?
Specifically, we need to ensure that traffic originating from WSL2 is correctly forwarded to the proxy service bound to the Windows loopback interface, while GlobalProtect Explicit Proxy remains enabled on the host.

Start by reproducing the stated setup: WSL2 traffic, GlobalProtect with Explicit Proxy enabled, and the PAC service on 127.0.0.1:9999. Inspect how WSL2 traffic uses the Windows Hyper-V loopback interface and determine whether a supported forwarding configuration exists. Done means documenting a verified way for WSL2 traffic to reach the host proxy, or clearly recording the limitation.

Written by the indexing model from the issue text.