Nope.
It can be done but it requires knowledge and effort and you'd have to share the result on the workshop if you intended to play with anyone else.

An example as to why would be as follows:
Say you care about MPI. If some mod uses custom AIPs (AI Plans), which determine how the AI behaves in reaction to the player(s), those AIPs often rely on custom path points that maps from another mod may lack. This would often result in the AIPs being broken in some way (read: possibly entirely).

Yea, unfortunately in the old days, it was easy to accidentally cause "bad assets" by mixing up map packs together loose in the "addon" folder.

BZCC fixes that issue to ensure everyone can successfully join the game, but requires the Config mod to include all the Map Packs desired.

To solve this restriction in some way, the mod type "asset pack" was created. This is not a mod that appears in the mod list, but instead is a "map pack" that a Config mod can add by simply including the Workshop ID number in it's Asset Dependencies string. It can contain anything from maps, to textures, or entire models/weapons/races, such as Hadeans.

This allows someone to make a Asset Pack workshop item, like a Map Pack, and then anyone that wants to include it in their mod can simply add it to their Config mod.

So, as an example: Person A makes map pack Alpha, Person B makes map pack Beta.
Person C wants to use both map packs in their mod, so they add both to the Asset Dependencies.

Person D wants to make another mod that only uses Map Pack Alpha, so they only add map pack Alpha's workshop ID to the dependency list.

This is the closest way people can make map packs, as individual components that can be combined together without causing file conflicts.