I agree that there is no particular value in avoiding a hardfork to fix an issue like this– particularly as the other chain ‘stops’. Were there a clean non-hardfork solution then it probably would be preferable, but abusing timewarp doesn’t strike me as clean at all.
It was also difficult enough to construct anti-timewarp fixes that were non-currently-disruptive and actually stopped timewarp– so I also have a concern about abuse potential ‘fixes’. I suppose if one was really paranoid one could make the timewarp fix just not active for the very end of the time range (leaving enough room for whatever shenagans might be desired there) and trust that the overflow fix latent hardfork will moot that long before that time is reached. This at least would leave no abuse potential before that point.