Ability to unload and destroy the editor instance or reload the config options?

In my use case, I'm trying to change the store and load URLs used by the remote storage manager dynamically. As far as I can tell, the editor does not pick up and use any changes to the config if I change them directly, ie. editor.Config.storageManager.storeUrl = 'blah' after the editor has already been initialized.

To try and get around it, I was attempting to unload the editor from the page programmatically by removing the target DOM element and recalling init. However, the init function seems to create multiple instances of the editor. I noticed the GrapesJS.editors array keeping track of them, so I tried setting this to empty to hopefully have the instances be garbage collected. Even in this case however, the editor has event handlers that still seem to trigger afterwards, saving erroneous data.

Ideally, I would like a way to either destroy the editor with some destructor method (if one does not already exist) or force a reloading of the config options without reloading the editor.