Hi @Deleted_Editor_1958914, and welcome to MusicBrainz - and thank you for your contributions so far! 
Yep, as the other posts have said, we’re aware of this. There are a number of issues though, first and foremost that our API/web service does not currently have any way to expose non-applied data/edits. There’s MBS-5628 for this. However, even when that is applied, there will need to be changes made to Picard (I couldn’t find any open ticket for this), and even then, what do you do if there are multiple open edits to a given entity and they conflict? (This can be by both multiple editors or a single editor can have made it so, likely without realising this (there’s at least MBS-7511 to try and lessen this).) Unfortunately, these are all rather large and complicated changes, and will thus not be likely to come around anytime soon. The edit exposing will likely not happen until we’re at “ws/4”, which is at least 2 years in the future.
In the meantime, you may want to look forward to MBS-9505 which will make it so you have 24 hours to make (non-destructive) fixes/touch-ups to releases you add yourself get applied instantly (currently you have 1 hour, which has proven to be too short). It will not help with fixing up releases added by others, unfortunately, but it may function as enough of a bandaid for now! 
(If you make an account on our ticket tracker, you can vote for the tickets, which may (but may not as well though, due to lots of other factors (e.g., how complicated it is or prerequisites)) make them more likely to get worked on sooner.)