I've never seen a case where mucking with the prefix to a long context pays off. Append a message to the session, do a compaction/truncation in the current session, or launch a sub-agent, all ways to inject new information from the harness without a big uncached read. I don't think that cache hit rate is very a useful metric to optimize for, much better to come up with an approximate cost model and benchmark task completions.