Don't disagree with concept – from a UX POV being able to "navigate" from one dialog to another be really nice.
But I'm not sure there is some simple shortcut here since RouterOS really does not know the relationships at some higher level than the commands themselves. Plus, I don't see MikroTik fork()'ing grep of an :export since they be same spot of what to "grep" (among minor problems that IP/CIDR need to be handled/resolved - so it's not just strings )
Basically, "relationship" between attributes is not in the /console/inspect schema data, even valid values are not always support. I actually wanted to implement a "Find Reference" in the RouterOS LSP I wrote, but there is no metadata about attribute's relationships.
I think you're up against the more fundamental problem that there is not some JSON/YAML/NETCONF/YANG/whatever representation of "the config" - which would have forced normalization. My hope is the long promised "controller" might have more config management features.