To me this sounds like an awfully stupid idea because it's a software engineering red flag. Code is supposedly designed around the need to simplify introducing changes where changes need to be introduced more often. One dimension of this requirement is minimize merge conflicts, and limit those to when you need to absolutely change the exact line of code some other commit is changing.

If your code changes are all over the place, touching half the repo and stepping on everyone's toes, your problem is not the version control system. Your problem is your changes, and the mess you are leaving in your wake.