Keep the two behaviors separate
If a clip plays smoothly while selected but briefly appears empty when its scene returns, write down both observations. They concern different moments in the source lifecycle. Re-encoding the whole file before classifying the moment can make the comparison harder to interpret.
Inspect whether the file is unloaded
OBS describes Close file when inactive as unloading media and notes a possible reload interval when it becomes visible again. Inspect that option for the intended source. The relevant tradeoff is between keeping the file loaded and the behavior required when returning; it is not a guarantee of a particular response time.
Use one owned clip and one ordinary return cue. Preserve the original option, change only that choice if a comparison is warranted, and repeat the same transition. Do not simultaneously change hardware decoding, resolution and media format.
Judge the audience result
Inspect the resulting transition in a short recording. A tiny operator-preview change may have a different practical effect in the finished presentation. Record the visible consequence rather than assigning an invented timing measurement.
If the gap remains, retain the source identity, departure state and return action for investigation. The inactive-file option is one supported hypothesis, not proof that every pause has this cause. No resource or performance test was performed here.
Questions answered
Does this setting change the source file?
It controls the source’s loaded state, not an edit to the original media.
Can I promise that disabling it removes every delay?
No. Rehearse the actual transition and report the observed result.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.