Hi Eugene,
ARI (Auto Route Insertion) in Juniper is the same as Reverse Route Injection (RRI) in Cisco:
In Juniper, ARI will populate your routing-table with static routes in order to reach remote subnets over the tunnel. This remote subnets will be taken from the "remote-ip" configured under the "traffic-selectors" configuration stanza for a specific VPN tunnel. This remote subnets also represent the remote proxy-ids of that tunnel. The following document will better explain traffic-selectors in VPN:
https://www.juniper.net/documentation/en_US/junos/topics/topic-map/security-traffic-selectors-in-route-based-vpns.html
As of now I havent seen a trafrfic-selector using 0/0 prefix, however the documentation states that this will be no longer supported (at least for "remote-ip" which ends up installing a 0/0 route via the VPN in the SRX's routing-table):
A remote address of 0.0.0.0/0 (IPv4) or 0::0 (IPv6) for site-to-site VPNs
Starting with Junos OS Release 15.1X49-D140, on all SRX Series devices and vSRX instances, when you configure the traffic-selector with a remote address of 0::0 (IPv6), the following “error: configuration check-out failed” message is displayed when performing the commit and the configuration checkout fails.
https://www.juniper.net/documentation/en_US/junos/topics/topic-map/security-traffic-selectors-in-route-based-vpns.html
If you are using a route-based VPN on the SRX side, then yes you could configure dynamic-routing protocols over the VPN and learn/share routes with the remote peers.
Now, I am unsure about what you are looking for on this part:
"Can I take advantage of RRI ?
I have a couple of ASUS AP's that can't seem to do without tunneling. I disabled teredo junk in windows but may reenable it."
Are you trying to setup dynamic VPNs tunnels against the SRX from those Asus Access Points? what does teredo has to do with the SRX? is it being ran on the Access Points?