Idea:
Make InEdit work for form components inside of a CMS_INPUT_LINK component.
Reason:
The InEdit functionality normally works with nested form fields, that support InEdit per documentation.
The only exception (to my knowledge) is the CMS_INPUT_LINK component.
It is a workaround, to just replace all CMS_INPUT_LINK components with FS_CATALOG components that are restricted to one item, but that is obviously not a good solution, because it is less usable in the SiteArchitect.