Well, if you want to be sloppy, sure!
Maybe I'm the only one, but I only keep a project's immediate dependencies and relevant hookups in the sibling base, and then only globally important stuff (world defs, climate defs, material.db, material/environment/*, player driver model) in the parent base. This way it's much easier to keep track of dependencies, and relatively easy to merge them to the project iff they get dropped from base.scs, etc. I don't like to include unedited base resources in case the player is also using mods which deliberately edit those resources; It spares the player from having to futz around with load orders any more than necessary. (And it spares me having to explain it a thousand times)
For example, let's say I make a trailer mod which makes use of SCS cargo models (and thus their texture dependencies), and many players also make use of a real logos mod which affects said texture dependencies. If my package includes those textures, the player now has to remember to place the logo mod above the trailer mod or else suddenly all their CATs are MUTTs again. I think you know as well as I do how great some players are at following directions and how ..."gracious"... some can be when faced with troubleshooting load order stuff.
TL;DR: I'm weird. But surely that isn't news by now.
Mwl4 is working on it 
