Job Data Modernization - Processing Historical or Retro Transactions

We would like to seek feedback with regards historical or retro change transactions using Modernized Job Data. We process a lot of these in our organization (e.g. retro data, pay change). We see that as delivered (when processing such transactions), the User is directed or notified to review and/or correct all effective date rows above or greater than the historical or retro transaction. If this is the case then updating the same and/or existing sequences will result to losing history on the data, versus adding or creating a new sequence for the top of stack to have the corrected data.