Yes, loading any parent tree will necessarily not cause any issues with moved, changed directories/files. It also stands to reason that loading any arbitrary tree would not cause you to “miss” any files.
What isn’t clear to me is if the chunking mechanism is necessary to detect if the actual content is missing in the backend. Say for example your do half of your first backup, then run prune (which because there are no snapshots the data is all removed), then you load some cached tree/log from the first backup run. Leveraging the ‘cached’ tree will cause it to skip some files, but will restic notice they are missing in the backend? Would it require a ‘rebuild-index’ or a ‘check’ first? @odin touched on this point:
But what wasn’t clear to me is if the check @odin mentions would be a new one that would need to be added or if it is already one that restic does.