Do you need other WiFi devices (like a phone or a laptop) to be able to access your servers? If not, you could just set up your desktop as a router, that would be the most painless way to go around this situation.

The basic steps are to enable IP forwarding on your desktop, configure a static IP address on the Ethernet interface (for example 192.168.1.1/24 - just make sure it is in a different network than what you get from the WiFi. For example if you get 192.168.0.x, the previous example address would be fine), then optionally set up a DHCP server on the Ethernet interface (otherwise you will have to manually give everything a static IP address), and then finally add a masquerade rule into the firewall (something like iptables -A FORWARD -o wlp0s1 -i enp0s1 -m conntrack --ctstate NEW -j ACCEPT; iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT; iptables -t nat -A POSTROUTING -o wlp0s1 -j MASQUERADE - the first two rules allow new connections from Ethernet to WiFi and replies in either way, and the final rule sets up the masquerade - it makes it look like all the traffic is coming from your desktop and hides the new network from your WiFi router; it wouldn't understand how to communicate with this new network otherwise)

It might sound pretty overwhelming, but it should be manageable if you go step by step.

I would personally do all the networking in a VM. You can create a VM with a virtual network interface connecting your machine to the VM and then use PCIe passthough to passthough WiFi and the network plug.

This is much more complicated but it has the benefit of not screwing up your host system. If you break the VM you can roll it back or recreate it.

You'll want to bridge your WiFi and Ethernet interfaces. As always the Arch Wiki has instructions for setting up a bridge interface, there's multiple options depending on how you have your network setup on your system: https://wiki.archlinux.org/title/network_bridge

https://www.google.com/search?q=linux%20bridge%20wifi%20to%20ethernet