Necessity is the mother of invention 🙂
Another approach is to take the initial list and add markers to the clips and not the timeline.
that way even if things ripple you’ll still be able to identify visually that you need to make a change even though it won’t match the time code.
there’s not a lot of magic to your problem in that the changes people are requesting are being made on a list based on a fixed timecode reference. As soon as you make a rippling change, your timeline will no longer match that reference. So the way you have evolved to approach seems the least impacting way to approach it.
If revisions were able to be identified based on the event rather than the timecode…then that would be interesting…but for now….seems like your on the right path.