To be honest, I still don't see how this is going to work with the Hub 3. They'll be two issues, firstly the 192.168.1.0/24 subnet is used for guest wifi (even if you don't use it) and I suspect the Hub will simply throw up its hands (metaphorically speaking) and not know how to deal with the situation. The second problem will be routing back to the second subnet from the internet, when incoming packets destined for this subnet hit the Hub, it won't know what to do with them.
There needs to be a route saying 'for traffic destined for 192.168.1.0/24, send it to (say) 192.168.0.199', where that is the VLAN interface address on your switch for the VLAN which includes that subnet. But already stated, you can't add a route to the Hub so it won't know what to do with those packets and will just drop them.
Of course if the devices on this second subnet don't need internet access then this won't be an issue. You really do need your own router, it doesn't need to understand VLAN frame tags itself as the switch will handle all the inter-VLAN routing but it will need to ability to define static routes on it.