Question About UMovieSceneCondition and bEvalNearestSection Limitation in Sequencer

UMovieSceneCondition is very helpful, as it allows me to delegate more flexible content control to the hands of the director.
For example, I’m currently exploring the implementation of a QTE system. By using different values from a custom gameplay system to control whether section are executed, I can achieve this functionality quite elegantly with UMovieSceneCondition.

If the interaction between UMovieSceneCondition and FMovieSceneTrackEvalOptions::bEvalNearestSection could be improved, it would be incredibly beneficial for this kind of use case.