HIVE

It depends on what kind of libraries you decide to use. The issue with using new libraries like DDS, Unit Indexers, etc, is that you force users to get rid of similar systems in their map since you cant have such systems coexisting. With this in mind, the spells already in their map that are dependent on the systems will break, since the spells wont be integrated with yours.

What kind of libraries do you plan on making yourself for your submissions?

Mostly simple things like projectile systems, dummy handling, etc. I guess there won't be a problem with those.
However, damage detection might also turn out to be necessary. I don't necessarily need a new system for that, but the way I use lfh's system is not modular without spending a lot more effort on it than is worthwhile.
I also manage my abilities with intermediate systems, so that I could put an ability in any slot I want. And to prevent a billion ifs all checking if a specific ability cast was theirs.
Unit speed modification can be done, but it won't combine well with normal blizzard buffs, so not only would it not work with other kinds of spells, it wouldn't work even with normal blizzard spells.

You plan on using vJASS?

Simple vJASS, yes. Libraries, private, public. No structs.

Hmm okay. Well the Code Moderators aren't big fans on people reinventing the wheel, but if you absolutely need to create new libraries, you will need to upload the libraries as a seperate submission first.

Well, the reason I would make my own resources isn't usually functionality, but rather standardization. When I make resources I always use the same logic for naming functions and that makes it easier for me develop stuff.
I do use some resources, such as lfh's DDS and Bribe's Unit Indexer. They are fine because there is very little API involved, so adapting to that isn't a problem.
It's also easier for me to keep things updated if I have my own resources, because I don't have to rely on anyone else that way.
That's my reasoning anyways.