Hey @teocomi !
Sure. 
I am currently developing a web app to view/modify parameter values of an uploaded Revit model. Similar to the ParameterPanther, but with some more functionality.
Therefore the app would have to know, which parameters are available in the original source model (Revit in that case) and could be edited.
In between I am filtering the parameters down to our company’s shared parameters, but this is just an additional step and shouldn’t concern the above topic.
I understand, that uploading empty parameters also can’t be the solution. And it should be a general solution. So I don’t really have one.
I’m not sure if that would be too specific for Revit, but might it make sense to add collection-wide parameter definitions (like project parameters in Revit) to the collection’s data property? That way, those (potentially many) parameters just have to be saved once and not for every single element (except it would have a value).
Then, you could also start thinking about just referencing/detaching it’s definition inside the element’s parameters, which would even save memory … but also would make things more complex to deal with. And I assume you have some reasons why you haven’t done this already.
On the other side, Revit doesn’t have parameters just for a single element (in contrast to userStrings in Rhino). So if I would like to edit parameter values for multiple elements in any kind of table, I need to know the logic of the model context and have to leave the per-element-level.