I may be a bit late to this post but as a contributor to both projects, I think the main difference here is that MusicBrainz is all about trying to prevent data

I may be a bit late to this post but as a contributor to both projects, I think the main difference here is that MusicBrainz is all about trying to prevent data deletions in favour of data merges, which will be resolved to the new object while OSM pretty much only cares about the look in the end. So in OSM it's perfectly acceptable to delete an object and re-create it whereas in MusicBrainz deletions are very much frowned upon. This means that you often can't really track changes to a single OSM object which would be pretty much necessary for implementing robust rollback behaviour.