+1.  I think that the scenario where two different consumers might try to override the same setting and not have any way of knowing that this had occurred would be really, really bad... so if we ever go to a more granular solution we're still going to need track overrides on a per-setting basis and throw an exception if two callers try to override the same setting.