Thanks Ryan!
We currently maintain our concurrency via multiple LRS Routes on top of one another and it makes finding overlapping data locations a real challenge because its only an overlap if its on the same RouteID. Gets a little hairy when there are five or more concurrent route segments in some places where only one route should actually have the data on it (dominant route, usually from RouteConcurrency output, but sometimes not because of dominance rules that have nearly impossible logic to script for!)
Looked like the functionality you referenced was on the pipeline referencing side of things, is that the same for Roads & Highways in Pro?
I seem to recall that ESRI encouraged us to use the event to manage concurrency as its less complex to maintain the route network (and a lot less edits there for sure).