Stab in the dark, but why not just create a second bridge on Router Two and give the bridge a manually chosen IP address on the 192.168.0.0/24 subnet (but outside the dhcp pool) and set statically in the lease (bridgeIPaddress=192.168.0.x). Anything attached to associated bridge ports would be in effect attached to router1.
So as stated the issue becomes how do LAN2 folks reach LAN1 and vice versa.
On router 2.
Forward Chain Firewall rules
allow dst-address=192.168.0.0/24 src-address=192.168.100.0/24
allow src-address=192.168.0.0/24 dst-address=192.168.100.0/24
In this way any traffic originating on one side or the other will be allowed to traverse subnets at Router 2.
You will need the exact same rules on Router 1 but flip the addresses.
In terms of routing, since Router 2 already has both subnets identified on its schema it needs less instruction.
However router 1 has no knowledge of LAN2 on router two and thus need to know where to send this traffic originating on LAN1 from behind Router1 and any return traffic
add dst=192.168.100.0/24 gateway=bridgeIPaddress[/color]