Definitely not worth it, just for the minor convenience such a feature might give an infinitesimally small number of editors. So you’d not only have to build a new edit mode UI for this feature, but you’d also have to rewrite the basic timecode tracking and housekeeping code throughout the entire app. For example, how does Resolve handle looping timecode on a single clip instance? Usually non-sequential timecode is considered an error in almost all workflows. It’s a neat idea, But this seems like such an edge case video editing scenario that I don’t think it’s worth adding to the existing editing feature set, because it would probably have tons of side effects that would require messing around with the code for the existing tools, which opens the gates to more bugs and regressions.