I never said you did the defaults-to-GTOL thing. Just pointing out another of the problems people create for themselves. IME, the best results have always been to create the GTOL datums right after the defaults and CSYS because if one is changing their GTOL datums, they are going to want to check every feature anyway to make sure everything is good to go.
I won’t disagree that the locator could be a GTOL datum. What I disagree with is that the GTOL datum is part of the locator feature. Make it a separate feature in the model tree. Then, if the locator has to change location, all the other features referencing that GTOL don’t get jacked up. Or if they would get jacked up because the GTOL is a child that moved with the locator (say, a GTOL axis that references an axis in the locator) it only requires redefinition of the GTOL back to its original position rather than redefinition of thousands of features. Separating it also makes it easier and quicker to find. As an added time saving bonus, users that have experienced this before will simply sever the one parent-child link before moving the locator in the first place.