Add config setting remote.<name>.annex-presence-ttl, such that the result of CHECKPRESENT|CHECKPRESENTEXPORT Key from that remote for that key will be cached locally and reused, with the cache entry invalidated after the specified duration. The cache can just be the location tracking info: if it has been most recently updated within this duration, just assume the key is present without contacting the remote. Maybe also, on a cache miss update the location tracking info with the more recent timestamp reconfirming the presence.
Then can also extend the external special remote protocol to let a remote send a batch inventory of its contents, which will batch-update the presence info, which will then be valid for the specified time.
Related: CHECKPRESENT-MULTI; export and import appendix; trust.
Using location tracking for this seems to trade off the time to contact the remote and check presence with bloat of the git repository. This does not strike me as a good tradeoff. If I were going to implement this, I suppose I'd store the information in sqlite instead.
I'm not clear what the use case or benefit of this would be?