The current Wiresock VPN Client does not support local Wireguard endpoints in the configuration file, rendering the method of redirecting WireGuard through the local proxy, as described in the provided link, unfeasible. I’m contemplating the inclusion of local endpoints as a feature, however, this isn’t necessary for your specific situation.
You can simply specify the applications you want to forward over the Wireguard tunnel under the “AllowedApps” configuration option. For instance, setting “AllowedApps = firefox” will result in only the Firefox browser’s traffic being forwarded over the WireGuard tunnel.
If you prefer to have your browser explicitly configured to use the specified local proxy, you can install a lightweight SOCKS5 proxy and include its name in the “AllowedApps”. Consequently, all outgoing traffic from this proxy will be directed through Wiresock over the WireGuard tunnel. This setup will also apply to all traffic from the proxy’s clients.