Quest 2, 3 & Pro - Connectivity Issues

For now it seems I succeeded solving the issue following the advices of BlackCat, I modified the mode of my router TPLINK Archer that was in AP to put it in normal router mode. So my configuration is the following:
1-A server from my FAI feeds a local network of all my connected devices in wifi 5, 5Ghz wireless as well as in LAN under a 192.168.0.xx adresses network using a DHCP addressing mode. It’s local adress  is 192.168.0.1
2-it feeds also by RJ45 cable from its built in Ethernet switch the WAN of a TPLINK Archer router dedicated to the wireless interface with the Q3 as well as the LAN RJ45 Gbit interface with my high end PC for PCVR flight sim using Virtual Desktop.
3-)This Archer is seen under the general local network at a fixed adress 192.168.0.191 through its Mac adress. It is itself configured separately as a 192.168.1.1 dedicated router and is not using its own DHCP capability to communicate with the LAN cable connected high end PC but also through a fixed stable adress at 192.168.1.167 using the PC Mac adress.

4-The Q3 is then connected wirelessly to the TPLINK using also the Q3 Mac adress and a fixed adress in the TPLINK dedicated network 192.168.1.143. Wireless link is done in wifi 6E at 6Ghz only  in 802.11ax with only 2 clients, 1 LAN is the PC 1 wireless is the Q3. Channels are 160Mhz auto (PC)

i played DCS 3 hours without a single disconnection with this configuration while I had generally 2 or 3 per hour while the TPLINK was in AP mode. Of course for multiplayer game I had to change my server port forwarding that was directed formerly straight to my PC to my router TPLINK and use a NAT forwarding of port inside the TPLINK toward the PC for these same ports (also adding this ports allowance in the windows firewall but it was already done before ). I will make more test duration next days and keep the community informed of the result. I am under the V66 firmware (last stable FW distributed in France) 

It seems over the past 2 months Meta has been doing everything they can to make the Quest headsets useless.

V65 borked the WiFi on it, making it harder to set up a new device or use the Pro Controllers.

V66 wrecked hand tracking, so basically I can put the headset on and look around, which I know I'm jinxing to be faffed up I'm V67.

C'mon Meta, we need answers, and we need results.

Yes, but this is not the point. I appreciate that buying extra hardware you were able to fix, but Wi-Fi on a Internet-connected device must be working in most scenarios without extra effort.