Quick answer: Go for it. Simplification is good.
Changing a snapshot build's configuration seems like an improvement to me, but it will likely break someone's workflow or some automated process, and they'll have to adapt. See also the earlier thread, Rationale for per-version user scope packages? , which started out as an argument in favor of the opposite change toward more sharing.
I haven't been able to contribute or even use Racket as much as I'd like in the previous year anyway, so the impact on my workflow should be minimal I guess. (If you'd like to make even more aggressive changes and I'm the only one likely to be impacted, please do proceed.)