Sure, it'll look bad in wireshark, but you can simply disable the reporting of OOO, and the stream is perfectly interpretable anyway.
Using Mode 2 or Mode 4 with xmit_hash_policy=layer3+4 (so you're load balancing on the IP/port tuple) still only balances one TCP stream out one slave.
An out-of-order might be common over the internet, but shouldn't happen on a good high-speed LAN connection. As we approach tens of gigabits, too much out-of-order processing will kill wirespeed bandwidths.
Considering people suggest disabling TCP SACK because the CPU overhead is (allegedly) too high on good working connections, out-of-order processing cost would be much higher.
All bonding modes except Mode 4 (LACP) and Mode 6 (ALB) are transmit-only. The receive throughput on a Mode 0/1/2/3/5 bond is still the max of one slave.
Round Robin delivers packets out each slave in sequence, but there is nothing in a switch which guarantees that packets will be delivered in the order received.
These TCP sessions will be suffering huge Out-of-order packets which makes TCP CPU and memory usage increase. It will get worse as more traffic is added to the switch.
This also makes your sessions very hard to troubleshoot, cos they'll be full of Dup ACKs and Out-of-orders so it's hard to spot a genuine fault.
Also round-robin is a transmit-only speed increase, the traffic coming back from an unmanaged switch will only come in one slave.
This is a messy use of bonding to "brute force" a speed increase and I wouldn't recommend anyone set it up this way.
I don't know a way to reliably load balance a single TCP session for faster bandwidth. Get faster NICs.