@cyberzeus Ok so I made this testing with the same set up as before and then changed the following:
A rule on the main pfsense to block all ICMP on the TestVLAN (kill states required for it to "kick in").
Trigger Level set to Packet Loss
State Killing on Gateway failure:
a. Kill states for all gateways which are down
b. Flush all states on gateway failure
Regardless of 3a or 3b, I see the exact same behaviour as before. When invoking the rule on the main pfsense, "Loss" starts to rise and soon after passing 20+, it switches over to WAN2.
Spikes now start to show up on the WAN2 graph and whatsmyip shows my correct LTE IP.
Toggling the rule off, and "Loss" goes down again and seconds after WAN indicates online, traffic shifts back and whatsmyip shows my fiber IP.
The only thing when using "Flush all states" (which affects LAN side states as well) is that the pfsense GUI appears to freeze for ~15 seconds before that session reengages. Using "Kill states" isn't noticed at all from a LAN to LAN perspective. This was of course true in my previous testing as well...