I would love to see any data you have to support your assertion.
This is networking 101 and it was part of my education. Because of such, I will always use it to grade even a SOHO IGD:
http://www.cisco.com/web/about/security/intelligence/network_performance_metrics.html
http://en.wikipedia.org/wiki/Throughput
Hardware architecture and (OS) software handling of the data did and still do not go hand in hand. Changes have been made to both to CPU handling, DMA memory loads, cache handling, transmit paths, zero-copies, packet scheduling, etc to allow networking performance to not only increase, but so as to not be as affected as much by the limitations of the CPU, memory, and operating system.
http://www.nanogrids.org/jaidev/papers/ispass03.pdf
Networking is actually very hard on the system's hardware, matter of fact the smaller the packet is the harder it is on the hardware (if you did not read the paper). However, these additions and changes to hardware do not resolve the issues of networking, and because of such newer features are created to handle the problem of a problem. One example is the HW-NAT accelerator of the RT-N56U which does packet aggregation, TCP/UDP offloading, NAT translation offloading, and a couple of other features. Note the difference with acceleration on and then disabled when the 74K MIPS core (not a MIPS networking core) handles most of the data.
Without HW-NAT
Client connecting to 10.10.1.1, TCP port 5001
TCP window size: 87.5 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.1.10 port 44672 connected with 10.10.1.1 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 361 MBytes 303 Mbits/sec
With HW-NAT
Client connecting to 10.10.1.1, TCP port 5001
TCP window size: 87.5 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.1.10 port 44674 connected with 10.10.1.1 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 1.10 GBytes 943 Mbits/sec
Your tests are not showing the over all picture. You do not take into account the cost of functions that the router performs such as packet sequence inspection (SPI), multiple concurrent user usage, etc. You are taking a flow of data and sending as fast as possible to one simple point of the networking fabric. I am taking your data and formulating it to seem what it would be like for my networking infrastructure. This to me makes the version 2 router inefficient and horrible for the cost. It would be asinine to purchase this router until properly fixed. If a user wants 3 streams for wireless, it would be better to get another router when considering the price premium to performance ratio. Is this not the very reason for your website? So it surprises me that you are trying to refute this.