I'm trying to understand what you want to do with a browser control.. if all you want is to make a way to check specific web pages (for weather, news, traffic etc) , then you should probably just make a stand alone application that you'd call from within RR (by pressing a button etc -- Dynamic commands can do that even without changing RR's code). You also have the option to simply use your app in the Launch menu.
How it works: Basically anything a user does in RR gets channelled through this "EXEC" function in RR. all screens are copies of frmSkin with added objects as needed, they are updated at a rate of 10 times per second (labels once a second) and that's it. I would strongly recommend not to add anything heavy like a browser control into frmSkin.. you can most definitely create a separate form for that (if needed) and then just control it from the other forms (that's what I did with the form that controls Speech, Media Player Classic and the one that holds MonkeyTalk to integrate with MM).
The least amount of stuff on frmSkin the better, the only things that should go there are things that might be used enough to appear on EVERY screen.
You can most definitely copy portions of RR's code to make your "browser" control app skinnable. And you could most definitely have normal controls in RR skins while running your separate application embbeded..