A couple of times now I have been caught out and reported an issue with a plug-in after an update, when all it took was a refresh to resolve it. Time and effort are wasted with this.
Proposed solution
I would like to suggest that a standard message gets integrated in Obs that pops up when the user has updated a plug-in, and the message should say that the vault needs to be refreshed (Cmd/Ctrl+R) for the update to be enabled properly.
I’m with @WhiteNoise on this one: if your plugin is correctly written to disconnect itself from Obsidian’s API, a reload should be unnecessary.
(Edit: I just realized you’re not the plugin developer; if you have a plugin that doesn’t work without refreshing, it’s a bug in that plugin and should be reported to the developer.)
I am saying that it should not be necessary to refresh the vault if the plugin is properly written.
We forgot to add code to trigger unload/reload plugins upon update.