can route 980 Mbps with 25 firewall rules and 512 bytes packet size.
512 bytes are fairly large packets. Most packets are a lot smaller than that. A lot of acks, etc. So the number you should look at is the one on the right, for 64 bytes. Mainly for two reasons, first it kinda provides a worst case scenario which is what you want to look at if you're looking for assured performance. Second, these are lab tests and not real world. When considering real world performance there's often other stuff going on on the router that also drains performance. You're usually NATing, the bridge consumes CPU time, OP will be marking packets for the 3 WANs he'll be using, etc. So even though some packets will be larger than 64 bytes and you may not be using 25 filter rules (10 is usually min but mangle rules consume about the same CPU time as filter rules), real world performance is still going to be less (sometimes a lot less) than those numbers.
So it all comes down to what he's expecting. 30 mbps up and 40 down full duplex tcp traffic over 3 interfaces can reasonably be expected from your suggestion. About 30-35 total will work from 750Gr3/hEX.
Well, each game is different, but this is my stats (from dedicated interface on a hEX Gr3, serving 18 L4D2 servers). Uptime is 9d 20:39:20. Interface is dedicated to the server. It is used by the served games and server upgrade.
With 13 occupied games, serving 39 users, I got about 3 Mbps of traffic. I don't know what games he will play, neither their bandwidth usage, but I have never heard of a game using 1Mbps/player in a match.
Tx/Rx Bytes 24200184794/53467186121
Tx/Rx 64 1285841/2231880
Tx/Rx 65-127 158537060/3797076
Tx/Rx 128-255 38668653/47841649
Tx/Rx 256-511 409764/72647785
Tx/Rx 512-1023 39767/21482513
Tx/Rx 1024-1518 1002087/2893012
Tx/Rx 1519-max 0/0