If it's bricking you are worried about, then actually doing some
rset commands over telnet has a lot of advantages.
With rset you can apply the settings live and do some testing to see if you get the results you want, without making those settings permanent just yet. So if you made an error, things turn out to be unstable, crash or whatever, you can just do a cold reboot and you have your old stable settings back. If on the other hand you change the .rsc file, then next time you boot up those settings are applied. So if those are the wrong settings, resulting in instability ... not so good.
Which is the long way of saying: to be safe better apply new settings with rset first over telnet, test it a bit ... and then when comfortable enough with that you make the settings permanent with a .rsc file.
Also, see
my post here for an example on how to use
rdump to save a part of the resource tree. As in, you make your changes (rset etc), test it, and then when done you save those settings to your favorite .rsc file using the rdump command.
PS: I've done a lot of mucking about with rset, and every curious state was fixable with either a
restartapp (most of the time this was enbough) or
restart (win ce reboot) or power cycling. IMO rset is pretty safe. As long as you stay away from the eeprom