I'd say that MVC pattern in enterprise stuff is applied because the need of having different views over the same model and persistent data. Whereas in games you'd apply it to have a clear distinction between systems as other users said said before (input, render, data).

It is a very "natural" pattern (like the layered architecture) so probably many apply it to some extent, knowing about it or not.

MVC got such an ambiguous and watered down high level concept you can apply it to nearly anything, even retroactively. Imo the main takeaway from it is to not intermingle presentation, business logic and data storage so refactoring stays easier, other than that you probably wont gain much from it.