What about implementing a time-based edit queue? ForFor example, let's say we set the threshold to five edits, with a time delta of 10 minutes.
If you make more thenthan five edits within a ten-minute period, all subsequent edits are sent to a queue. TheThe edits in the queue are done immediately (the content is changed instantaneously), but they are pushed to the front page one at a time after a certain amount of time (maybe 5 minutes).
(Basically, your edits go to a queue if you exceed 5 edits in 10 minutes. AfterAfter that, all edits are delayed being pushed to the front page by five minutes. AnyAny subsequent edits, while there are still entries in the queue, are further queued.)
Furthermore, since sometimes you want edits to your own questions/answers to appear near the top, this should only apply to edits you perform on someone else's post. If this was implemented, there would be no need to view an edit queue (except for your own), and if that particular edit was rolled back, it should be removed from the queue.
Finally, some people have worries that their "essential" edits would not be pushed to the front as quick as they would like. ToTo mitigate this, maybe there would be a way to flag an edit as a "priority edit", so it would be put in the top of your edit queue (and would be placed on the front page in the next push interval).
Thoughts?
Also, maybe strictly tag-edits should not be pushed to the front page (but still show up on a user's edit history, of course)? I do not think we should implement a "minor change", because as some have said, it reduces the visibility of user edits to the community. ThatThat being said, I think that just tag edits could be an exception to this rule.