Recording impediments is a great way of highlighting problems and their cost across multiple Scrum teams. If you track them you can see how long they take to close and how many there are to help discern their real impact. Without this visibility some will end up in a release retrospective as minor issues and are often unquantified.
A regular small delay may not be a teams highest priority but what if it affected everyone and regularly? The real cost may be far higher.
I often find it helpful for the Scrum Masters to get together and discuss the main impediments. Attempt to quantify them in terms of re-work or cost of delay. If everyone gets together and tells you that the lack of data is now going to cost 8 weeks of effort, then the next sprint it’s 12 you will have more of a case for someone to act.