Removing the Killer Control Panel or the drivers to load Microsoft provided drivers leaves the "Killer Network Service" installed and running. This is even installed by Windows 10 Updates on a new installation.  The solution is to stop "Killer Network Service" and set it to manual or disabled with the Services window (services.msc). It can be delete via the Command Prompt and the "SC" command.  Also, I should ad, this is not a Wi-Fi only problem, this can cause you problems on ethernet too when trying to access some IPv6 sites. 
I have a R11 purched in December 2020 with a R10 purchased in December 2021 and I never really used the R11 much, but I am using the R10 a lot and I am experience a problem with accessing [URL] via their IPv6 addresses. I have to put a IPv4 address in my HOSTS file to force it to request the file via IPv4 so I don't have that trouble. Rapid reapeted Ctrl+F5 may load the file.  Chrome will say "This site can’t be reached The connection was reset." ERR_CONNECTION_RESET and Firefox "Secure Connection Failed" PR_CONNECT_RESET_ERROR.  If I try to load a page that hs the js file as an include in the header, the console on Chrome says "GET [URL] net::ERR_CONNECTION_RESET" while FireFox says "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at [URL] (Reason: CORS request did not succeed). Status code: (null)." The R10 has a Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW) running Windows 11. The R11 has a Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) running Windows 10. They are both running in 802.11ac, although I can force them into older protocols with no luck.  I have updated the drivers from Intel on the R10 with no luck. There is a thread about this here [URL] where 2 others have said they have Dell computers with the same problem. You might gain more insight into the trouble on that thread.  The AT&T router/wifi was installed only a few months ago and it works fine on my HP Desktop that I bought in 2017. Being this happens on 2 similiar Alienware desktop, it appears to be some sort of problem with the 2 desktops. Another odd problem is that sites I have no problems with, if they are IPv6 and are reachable, will timeout on the first ping hit and then are successful on the other 4. I can ping again and it then will be successful on the first ping. A while later it may fail again on the 1st ping. This does not happen on my old HP desktop.  Does anyone know how to fix this? 
RT10 & RT11 WiFi Problems With Some IPv6 Sites