reading all the comments in the forum about ros3 and accordingly to our experience, I would suggest you to implement ros 2.9 on RB333 (and newer hardware such as RB600). At the moment the ros3 is unusable on (accordingly to our experience):
wireless is not working, very unstable
OSPF is not working as expected, sometimes the routing tables are not updated correctly
PPPoE does not work at all (we opened a ticket in rc10, partially solved in rc11 but it looks like the problem was not totally solved)
Considering that we use mainly these 3 features, it would be helpful if you implement quickly a 2.9 version in order to use RB333/RB600 otherwise I guess almost everybody will try to find some hardware where to run ros 2.9.
The problems you mention are very specific, and if you read other posts, you will see that most people have no problems with what you wrote. We are working hard to fix those things, but is simply technically impossible to add RB333 support in 2.9. If we would do this, 2.9 would become equal to 3.0
Wireless is working with us, but unstable in a sense. I posted in other topic that if I try to change a setting on one wireless interface running as an AP, the other wireless interfaces running as APs disconnect their clients and reconnect them.
PPPoE works just great and didnt give us any stress even after upgrading from 2.9.42 to 3RC10.