No list but here is a KM document for making it work with F5:
JOLT "NwHdlr:Network Error: J_CHALLENGE FAILED\n bea.joly.JoltException" error when making connection to Tuxedo Jolt through F5 Load Balancer (Doc ID 1527794.1)
Note: for the Tuxedo JSL/JSH side an environment variable is used and for Tuxedo releases 8.1,9.1 a minimum rolling patch level is required
(from 10.0 on change is in GA release and no RP is needed)
Tuxedo is agnostic about which hardware load balancer is used. It should not make a difference.
WSL/WSH have behaved better than JSL/JSH(both use workstation protocol). WSL/WSH did not have the problem mentioned above.
The only other thing that comes to mind about hardware load balancers is transaction affinity. Using domain protocols any hardware load balancer
might cause an issue for transaction affinity by not routing follow up messages to the same domain.