mtucker
The answer to your question is "the geo clip sequence LOP". If it's not working as expected, or not generating results that work for you, then please provide some kind of example/demo file that shows this happening. This is the intended and expected workflow, so if it's not working, we'd like to fix it.
Loading a properly structured value clip into a scene should not cause all the clip files to be opened at once. And the geo clip sequence LOP should always be authoring properly structured value clips.
I did notice you saying that you sublayered the value clip file into your scene, which is a bit unusual. Generally when working with value clips I've seen the referenced onto a stage rather than sublayered. I don't think that should matter, but it might be worth testing...
I did some tests on storing valueclip, using the 20.5 version of the geoclipsequence node.
This is the problem I encountered many times in my tests:
If you directly use an existing file (bgeo or vdb) to link, when loading the valueclip, all the linked files will be read once before refreshing the data in the window.
Only after turning on Flatten Clip Files and regenerating the existing geo into a usd file, the read valueclip file can be read correctly according to the corresponding frame number. It will not read all the cache at once.
The same problem occurs when using sublayer and reference nodes
It is recommended to use a large cache to test, so that you can intuitively see that the hard disk reading speed is completely different.
I have also tested it on many machines and with the 20.0 version.
Is there any other way to solve this problem?