There is no NAT involved with the EAP1750H; I've got that being handled by the ISP fiber device, the Quantumfiber (Axon/Gemtek) Q5500XK.
Both my EAP1750H and R7000 are being used as APs only -- after Quantumfiber totally screwed everyone with their wifi pods going sideways (taking Plume out as the backend provider, wifi6 pods not working with new app, general chaos, so I went back to my old devices as APs.)
If you mean the active upload ping latency showing like 100ms or so, thats 95% because I'm using 5ghz between walls and at highest MCS it drops a packet here and there. But it still has decent throughput, and normally there is no problem in everyday use. Until I get a new higher-end router (x86 or newer ARM vs the years old 802.11ac stuff i have now) I won't be able to utilize SQM at full line-rate of 500mbit/s symmetric, so for now I just let the ISP gateway do the heavy lifting.
I've tried both 23.05.3 (still 310mbit/s) and Snapshot as of September 2 2024, (342mbit/s max, which isnt much of an improvement)
So I'm not sure this is the cause/solution.
Also, i was wrong, my device has a QCA9880 not a 9888 as I was thinking at first. It is a 3x3 A/N/AC chip with matching 3x3 antenna set. 5ghz only on this particular PHY even though the chip itself claims to support 2.4, its not wired that way in the AP. It is on a mini-pcie card.
I have a DAP-2610 (ath10) and I have the "same" issue as you, I get more upload speed than download speed (only by wifi) in wired I get the same full speed.
# run backlog per CPU
net.core.backlog_threaded = 1
# early packet sorting may or may not work well
net.ipv4.ip_early_demux = 0
net.ipv4.tcp_early_demux = 0
net.ipv4.udp_early_demux = 0
# dont rip qdisc timers off idle CPUs.
kernel.timer_migration = 0