Look carefully at your design. It strikes me that you are approaching this in the wrong way. The point is that a Rich Text field is meant for allowing rich text editing by an end user. If you are hand-editing the source tab, that's already a sign that something's adrift. Tridion is a web content management system, so it won't surprise anyone to find that it's focused on producing web content. So when you tell us:
We require decimal code as is in source tab because this code is used in some other tool to perform certain operations.
I'm already thinking that this is like going to ferrari.stackexchange.com and asking why you can't get half a ton of potatoes in the back.
I'll assume that you have a good reason for wanting to produce specific code in your output. The question is - why are you using an RTF for this? An RTF is focused on Rich text editing - and your output will be transformed. If you want to create literal text output - that's very easy. Use a text field, and arrange for it to be edited by people who can be trusted to put the desired characters one after the other in the correct order.
In order to execute the XSLT transform, the XML of your Rich Text field is loaded into an XML Dom. There's no way round this. The XSLT actually executes against the in-memory representation of the XML document, so by the time it runs, the 'decimal' serialisation of your character is already gone.
The problem then is how to ensure that your character is detected and output as you desire in the serialised output from your XSLT. It turns out that XSLT 2.0 has specific support for this problem, so you should look at character maps to see if they will work for you. I don't know a way to do this in XSLT 1.0, so if there's a reason why you have to use that, then Nick's suggestion of doing the replacement afterwards is a good one.