I wonder if you could apply this principle by writing a tool that goes through your git history and identifies distant regions of code that are often changed at the same time, so you can take some action to link those regions. At a minimum, adding "see also" cross-references, if not refactoring to bring them closer.
This is one of the key concepts in how Codescene analyses a code base by mining the Git repo.
It is quite useful to find find problem areas and tacit knowledge such as “when you change this API these two client side adapters should probably also be updated”
