EmployeeEmployeeHi Tom,
It has occurred as a possibility, yes. I believe it may already have been done. The problem is reliability - each hop would be an instance of the DataSource, which means if a route changes at all a hop may disappear (no data) or not be recorded until Active Discovery next runs. For routes that change frequently (particularly if they change in response to a routing problem) the returned data would not be particularly useful or reliable as a means of generating actionable alerts.
As a diagnosis tool (rather than a pro-active alerter) the ConfigSource will allow a 'collect now' action, so for troubleshooting you can quickly and simply get a capture of the current route and hop times.
