I'm not planning on implementing that, as what is in the pipeline for beta release this week (tonight?) is multiple, prioritized profiles. The linear approach is being replaced, as it's not easily understood (and this new way is a little more flexible). The way that it works is that if a profile does not exist in your, 'stack' it is not included on load and it is no longer displayed in the list when edited (versus having a line that says, 'Unable to locate some profile that I have no record of its name').
And now the reasoning for changing identifiers for those reading along...
Profiles, from my perspective, are self-contained units and are never meant to be used as part of a group. When a profile is exported, you'll notice that the identifier changes (as well as the identifiers of all the commands). It is no longer the same profile... it is a COPY of your current profile (with copies of each command) which may or may not be imported BACK into your current profile set (profiles created by you or by somebody else). So, at some point the identifiers will need to be changed and as sharing profiles becomes more and more common, identifiers will need to be changed all of the time. It's a design choice (necessity) is what I'm trying to say