That is more a reason against it than for it. You should not couple addon loading to GearSwap at all, and enabling one would encourage the other. It promotes sloppy design, because it ties the features of one addon to another, and without one the other won't work anymore. If GS breaks after an update, for example, all your other addons that you load through it won't work anymore. I know people are abusing GearSwap for that, but they shouldn't, and I see no reason to support them doing so.
That said, you can still load/unload even if it's already loaded/unloaded, not like it will crash the game. It will just display an appropriate message. So even though this is a bad idea, adding such a list wouldn't make any difference to your examples, they would pretty much work as they currently do.
actually the gearswap one i use when i change jobs so i dont have addons loaded for jobs that dont need them
i.e.
blu main/sub azuresets -- only needed for blu useless for all other jobs so it can be unloaded when not blu
cor main/sub rolltracker-- only needed for cor useless for all other jobs so it can be unloaded when not cor
there are more MobCompass,PetTP,autocontrol,etc. but all of these are only usefull for one or specific main/sub jobs
but my main reason it to cut down on extraneous info in the command window i.e. errors that dont need to be shown just because the addon is already loaded but if you type it in to the command window it should tell you if its loaded with an error
and i do know that it does not cause ffxi to crash but my second(smallest) reason if an addon has issues with an addon/plugin thats already loaded it can eather not load the new addon/plugin or unload the old addon/plugin(rare but does happen)
if windower.addons.list():contains('<addon>') then
print("<newaddon> can not be used because <addon> causes errors with <newaddon>")
windower.send_command("lua unload <newaddon>")
return
end
*also would work for plugins as new addons replace the old plugins