@Udbytossen Without knowing exactly your data flow paths, and which interface is which here, since you didn't include the interface those rules are on.
I would switch back to floating states.
https://www.netgate.com/blog/state-policy-default-change
See if that corrects the problem your seeing.
If that fixes it, then look into the details of why so you can adjust so that you can use the more secure bound to interface states if possible. This may require a look to your actual flow of data.
I can see your doing policy based routing with your gateway set on that last rule going to torguard. Not sure the point of the to lan address rule. If I wanted stuff to get to the lan from from this network your routing out your vpn connection, the destination should be lan subnets, not lan address. All that rule is going to allow is access to the pfsense lan IP. nothing else in the lan would be allowed by that rule.
This seems like a odd rule, why would devices need access to the lan address if they are on the tv subnet, wouldn't they access services on pfsense like dns or ntp on the tv address? Which you allow.