Like if you have some code that's been intentionally obfuscated, or made by somebody who names everything "a", "b" and "c", a LLM is likely to be of at least some help.
And yeah, you can do things like finding all the places where func() is called, but a LLM can also be helpful in saying where something needs to be done, which is a much fuzzier task.
Usually, If you don’t know that, you shouldn’t modify the system either. Just because you know how to unscrew a bold, you shouldn’t go about removing the head cover of an engine. Locating the area of interest takes a lot less time than actually understanding how it integrate, the guarantees provided by other systems and the guarantees that it offers.
Modularity in software architecture. By reducing the links between parts of the code, it’s easier for someone else to navigate the system and answer these questions. But it does require careful design and caring about the code.
In my own projects I'm also quite capable of forgetting stuff. Double checking with a LLM whether I forgot about one of the more obscure corners doesn't hurt.
Nit: not all of those questions require statistical language models. IDEs like IntelliJ have been adept at syntactical queries and refactors for many years using purely deterministic data structures and algorithms.