Here's the thing: I usually play Minecraft with over 50 mods (a little excesive for some, I know). So, it would be very, very helpful to have to organizing options (or principles):

1. Clear dependency tree: Often times it's hard to see which mod requires which other mod until the mod loader tells you something is missing. Now, I get that CurseForge already downloads the dependency for you, that's not what I'm talking about. I'm talking about "debbuging" what is causes the game crash in certain instances, which can only be done by removing mods until it runs okay, or, adding them one by one. In both cases, it be useful to know which mods depend on which other mod so that it's easier to go through them and cherry pick those we need.

2. Mod grouping: Similar to the previous point, with so many mods, it's hard to identify which mods are for which enhancement. Although that is no one's fault, really, just having a large list of files with abbreviatures and version numbers makes it more confusing. So, it'd be usefult to have a way to sort mods into "folders" which can be turned on and off. That way, "on" folders download the mod (if not already present) and "off" folders deletes them, but without removing it from the modpack. This too helps with the issue of selecting one by one the mods to load for "debugging". Note that these folders cannot (in my mind) duplicate mods to have like different versions of the mod list. The folders are meant to group mods to see clearly which ones refer to, say, "minecolonies", which is a mod for Minecraft that adds a colonies feature and requires quite a few other mods. Which ones refer to lighting and shaders and stuff, et cetera. It could be used even if we're experimenting with a list of mods and we want to balance them, so we classify them and turn them on and off to test results in gameplay.