I have set my show up on 192.168.2.0 subnet, so it's just the show controllers an Pi's. The home network is 192.168.1.0. I have my router for the show connected to the home network by the wan port. I can see the 1.0 network and Internet from the 2.0 side, I cannot see the 2.0 from the 1.0 side. I have a route set up on the 1.0 router that sends traffic to 192.168.2.0. Through the the wan ip of 192.168.1.130.
Even if you could get routing to work, the problem is that some (most?) controllers don't allow you to specify a default gateway.
e.g. in a E682, though it has a subnet mask (for who knows what reason), you can't tell it where to send traffic that doesn't belong in that subnet.
So you're basically stuck having to be in the same subnet as the controllers anyway.
wftxlites's mechanism achieves that. So does just renaming all of your 192.168.2.x devices to 192.168.1.x.
I'm not sure if you're trying to do isolation here to reduce traffic overlap - but you don't need subnets for that. Just putting your show on a separate Ethernet switch from your main network will achieve that.