The Q & A below can help you better understand the capabilities and limitations on virtual routers.
Can different VRs on a single device support overlapping RFC1918 address space on separate networks? VR-A has network A with 10.0.0.0-10.16.0.0, and VR-B has network B with 10.8.0.0-10.24.0.0.
Yes
If I can support overlapping addresses as described above, can I have duplicate IP addresses on different interfaces on different VRs?
No, the same IP on different interfaces is not supported regardless of different VR.
VR1-eth1/1 with IP 192.168.1.1/24 and VR2-eth1/2 with ip 192.168.1.1/24 will not be allowed.
However you can have VR1-eth1/1 with IP 192.168.1.1/24 and VR2-eth1/2 with IP 192.168.1.2/24. That works.
Can I redistribute routes between VRs?
Usually the recommended approach is to use a static route to point to another VR for routing and to use a static route for the return traffic.
Yes, you can redistribute routes between VR via BGP. I have never tested with OSPF, so I dont know but I believe they might be a way to do it via OSPF. There would probably be limitation in topology so I would still recommend to do it via BGP.
Our routing tables are relatively small. Can I manage/quota the number of routes available to any one VR?
Yes and no. The max number is system wide, but there is no option to define max number of routes per VR.
However, you can play with the Redistrib profiles/import&export rules on the VRs to control how many routes are advertised or received. Or you can aggregate to limit the number of routes.