It's either in OTP or just encrypted there. You can find it Base64 encoded in process 21 @0x0013F7A0 if you dump it.
Afterwards, convert it to hex and then back to Base64 with these sites:
http://tomeko.net/online_tools/base64.php?lang=en
http://tomeko.net/online_tools/hex_to_base64.php?lang=en
Once you're done, you could modify it in RAM by using this NTR Debugger code:
write(0x0013FAA4, tuple(map(ord, "
Insert device cert here")),pid=0x21)
The server won't accept modified CTCerts, they use the same signature types used to protect Bitcoins.
You're probably just getting a CTCert from one system and using it on another, and boom, problem solved.
If you're even being serious, that is.
I could do that by dumping anyone's process 21 and then extracting its DeviceID.
If you're just modifying it in ITCM according to the DeviceID you want to use and then modifying the DeviceID using your own binary, that means the 3DS can sign CTCerts, apparently.