What you suggest is both high risk and will only be testable once per payroll cycle.  "Glitches" mean that you've got a bug, again that your software has a serious quality issue with this update to 2023.  Your suggestion that we do this complicated step is unacceptable.

There is a risk that we wind up with a tax witholding issue if something goes wrong here.

You've coerced us into paying far more for this than we were paying while at the same time providing flippant answers that risk more incurred cost than this has already taken.

What else can you do to diagnose whatever this update has corrupted and repair the data?