The SC5 files are meant to be used at the direction of Harris TAC. What rescue161 says is accurate, each radio is different and each SC4/5 file was typically created by TAC and given to the customer to 'solve' particular problems that didn't warrant an immediate firmware release. Think of them as hot-fixes for software issues, TAC would send them out to see if the issue went away and then roll that patch into the next firmware release. These patches basically just altered an EEPROM value after the radio was written, e.g. ProGrammer would write 896.000 MHz to the radio and then the radio would "adjust" that to 902 on first boot. That's why, when the radio was read back out, the values would be un-adjusted and ProGrammer would error out.
The SC4 file format from years ago was reverse-engineered from an SC4 file that was created to move the bandsplit of the Orion radios slightly for a customer. Once the format was figured out, SC4 files were put out in the wild that could adjust the bandsplit of just about any Orion radio. This same patch format was also found to work with the M7100.
SC5 was the new file format when ProGrammer was replaced with RPM. The file format itself is exactly the same, and the patch is entirely dependent on the radio it's applied to. So far, only a handful of the patches were able to translate to more modern radios. AFAIK, there have been no publicly-avaialble SC5 to move any OMAP radio out of band. The file format is the same, it's just not what the radio is expecting and disregards it.
There are 2 ways to move the x5300 900MHz radio out of band. Either edit the frequency table in the code upgrade file and flash the radio, or find the correct SC5 command to do it on-the-fly. Both are extremely difficult to do outside of help from TAC. I'm sure a TAC engineer would read this and laugh as they look at the formula for how SC5 band-edits are made, they just haven't been leaked to the wild yet.