Trigger on change to versioned settings in snapshot dependencies

Hi

We have a build set up with a schedule trigger plus associated settings to detect VCS changes in snapshot dependencies and this is behaving as expected.  

We'd like to extend this to trigger on changes in the relevant versioned settings as well, but when I add the VCS root id for the versioned settings repository to the trigger rules I get a "server health issue" flagged that the build is not attached to that VCS item. This is technically true, although all of the projects and build configuration entities are tracked in the versioned settings repo.

My question is, in order to trigger on changes to versioned settings anywhere in the build chain, do we need to explicitly attach the VCS item for the versioned settings repo to every build config in that build chain or can we just attach it to the scheduled item at the "top" of the chain ?

More generally, if changes to build configs etc are being recorded in the versioned settings repo then should it be necessary to explicitly attach the corresponding VCS for that repo as well ?