unBaking or "baking with history"

This is a little odd question (or suggestion), I know. But I'm sure many people have had similar thoughts on this is it possible in some way.

Can you bake geometry with history? not only colours, but entire 'creation process'?

What I'm trying to say is, my definitions is getting overwhelmingly large 50+ sliders and parameters is making my cpu work for the money. 

Lets say I am working on a small brick, a part of a larger structure. I want to "build" with copies of these bricks manually (i know eeew, directly in rhino). This is done with "bake geometry" -> "play in rhino". 

But lets say I after all this manual brick building want to change a single parameter in one of those bricks, or more interestingly those groups/bakes with the same properties.

This function is seen in Sketchup and called "make component". A component is a group-entity that can be edited and all copies will be too.

As I understand GH, once a brick is defined with all its variable parameters and baked - it is a "entity without memory". I will bake multiple units with the same properties. Then make another set of bricks with other variables, nothing is stored. 

Imagine after baking a geometry to Rhino and the gh-def-itself is stored as a attachment/link of that geometry! Once a copy of that geometry is performed in Rhino, the gh. def is copied as well. Select the geometry in Rhino - and click edit in gh.

I know it is much to ask but it would be very very cool if this could be done in gh.