Don't really get the "I don't use factory presets", "I do things _X_ way" arguments... Some people do find factory presets to be helpful for one reason or another. Different people have different reasons for owning a Helix, as well as different interests and use cases for working with it.
As mentioned, I'm interested in noticing when factory presets are added/changed/removed, without having to expend any manual effort on doing so. For example, the "DLX CHRIS BUCK" preset was replaced with "Buck Mild", where some models/parameters/routings were changed. Because I'm aware of this, I can now A/B the two presets and explore how/why Chris Buck, an artist that I follow, chose to update his preset and potentially learn something in the process.
My workflow involves many setlists/presets including factory, 3rd party, and custom. These are backed up, organized, and version controlled; so there is no worry of finite space. They are used in different contexts. Jams, production, exploration, inspiration, replication, etc. Sometimes I might want to dig into tweaking models/parameters/etc., sometimes I might want to have a filtered down selection of presets that I've already vetted to select from, and sometimes I might want to find something new/different/specific.
I share the same sentiment @ “Let’s put real Names to the Presets/Models”. Some people will find that helpful for their workflow. The primary reason they're not labeled as such in the first place is legal reasons, not practical reasons. What benefit is there to people having to learn a brand new set of names for something they are already familiar with? It's a hinderance to workflow, as it prevents them from using domain knowledge that they've accumulated over years and instead have to either create a mental/physical mapping of real names to legally-allowed names, or spend time building familiarity with the models from scratch.