Not likely to happen in this way, in part because pure mode has to filter files from early game launch, having any configurable policy is very difficult, if not impossible.
It’d make more sense (from a technical perspective, but also for predictability towards both server owners and users) to have use cases like this able to be added in a supported way (not requiring editing arbitrary meta files with a broad scope, or raw game RPFs) and then permitted in pure level 1, or more granular levels be added ‘in between’ - as the initial announcement said, the current makeup of level ‘1’ is very much subject to change and we were expecting a lot more user feedback already. 
For example, for this case, we’d also have to know what exactly people are editing for mods like this - what files are in these .rpfs? what is changed in mapzoomdata.meta and minimap.ymt, and why? - and actual example files would help a lot with making a proper way to customize client stuff like this without requiring server owners to formulate meticulous policies with exact filenames, while also not confusing players with ‘why do my files work on some servers but not others?’ as ‘some mods allowed’ would be a consistent set.
(similarly, ‘Sound FX Replacement’ should be working in pure level 1 already - any example of something that isn’t?)