There are some offloading options that may be available for your device. See this thread as a reference.
If you don't see offloading options, though...
Some vendor supplied firmware includes special closed-source/proprietary hardware acceleration libraries for the routing engine. This means that OpenWrt doesn't have access to the code to enable faster hardware/software flow offloading for some chipsets. In those cases, you may find that the vendor firmware (or in some rare situations, alternative firmware that has a license to use these libraries and/or can use pre-compiled 'blobs') will be significantly faster than what OpenWrt can provide on the same hardware.
No worries. Your comment makes sense and is not wrong in a general sense.
I'm far from knowledgeable about the intricacies in the deep hardware/code, but I understand about proprietary systems. That said, as noted, it does appear to be an issue in the code, as noted by @egc in my original post with the question about the issue I was noticing. Thusly, I brought it here.
I am always a bit hesitant to build for other people, if I brick my own equipment so be it, but bricking someone else's is different.
But if you really want I can make a build for your R7500v2, but the devs are working on a solution, they have taken the matter upstream to the kernel developers, which also means it can take a while.
I have just looked into snapshot/6.1 and looking at the code I expect the same problem for which this patch might also help (with the necessary changes) but i have yet to build and test
Much appreciated, and I may come back and request it at a later date. This router isn't really critical to me and I only pressed it into service again after having been annoyed with TP-Link's Mobile App Only management interface. If the r7500v2 bricked, I have other options (like an r9000 i really dislike and the Deco mesh--heck I could default to OpenWRT on a Proxmox box if needed).
That all said, I'm ok with waiting for now. I'll just run the router on alternate firmware (dd-wrt) which doesn't have this issue (yet?) in the interim.
Yes...hence my desire to move to OpenWrt as the development appears to be more active. I'd move to the r9000, but it's still not "offically" supported, I really dislike the non-removable antenna (I have a different system for mesh WiFi), and the dual internal routers just confuse me. I should just by a UDM-PRO SE .
Important patches are still back ported so I am not overly worried and the devs over there are working on an update to Kernel 6.1 but that will take some time and effort and will likely come with the problems we are facing now.
The R9000 has a very powerful CPU but radios tend to fail, it has basically two switches which are daisy chained but that is confusing indeed.