The thing is what you understand by default :).� Because if you are adding shortcuts dinamically to morphs like:

morph := SomeMorph new.
morph attachKeymapCategory: #someShortcuts.
morph attachKeymapCategory: #someShortcuts2.
morph attachKeymapCategory: #someShortcuts3.
morph attachKeymapCategory: #someShortcuts4.

...
morph attachKeymapCategory: #VIMShortcuts.

when will you consider the default?� Maybe a default is with no shortcuts at all...

Then you may need a static configuration... Or a more intelligent way to store shortcut configurations per morph.
Or the capability to freeze them at some point in time and then go back to that state? But then you have to decide if you can override state, or storing all the checkpoints...

I think we need to find some use cases that need this kind of behavior, so we build the right abstraction...