I suspect I'll be creating a lot of snippets that will only be used as imports, I'll never call them directly into for example Evernote, only using them as a subpart of a snippet that calls them in itself. To illustrate using an example of a snippet with a shortcut of /gettingstarted with optional import snippet shortcuts of #a, #b, and #c, I'd use the /gettingstarted snippet but would only ever use #a, #b and #c as imports to one or many other snippets.
I'm concerned that this is already causing a cluttered dashboard and field pick-list. Since we can't nest folders I can't create a logical structure to handle this, and have currently opted to name snippets that will be used starting with "/" and snippets that will only be imports with "#". I tried putting the # snippets into a folder and disabling it, which does remove it from the picklist, but apparently it disables the imports so the other snippets can't call them. I'm now moving the # snippets to a #folder so they don't clutter up my category folders and make them difficult to scan, but perhaps there is a better solution that I've missed?
If there isn't anything I've missed, I'd like to suggest that some new functionality is added to stop folders and pick-lists getting cluttered with import only snippets. I think a quick win might be to supply a snippet level option to toggle on/off visibility in the pick lists. It would also be helpful if setting this toggle to "on" would cause these to have a visibly less prominent appearance in the Dashboard folders to easily distinguish them from the snippets I'm actively using.