Saying no to that change isn't about avoiding risk, it's about the time and money to code, test, and move to the production environment a change that while correct, doesn't change the way the program functions in any way.
Considering the software does function properly right now, and isn't about to break because of that, and that programatically correct internal printer managing software probably doesn't have anything to do with the company's bottom-line, making the change right now doesn't make any sense.
You make a note of the issue, and slip in a fix the next time you have to make a remotely consequential change to that software.