I don't think disabling of overcommit implies that physical pages are mapped immediately. If caches are instantly droppable, you can use a page that's allocated but unused for cache, and drop the cache page (and zero it) when the allocated page is written to.
You'd still have all of your caches until you have memory pressure with actual data written (but of course, with overcommit, you'd drop caches then too), but if you attempt to allocate more than you have (including through fork attempts as discussed elsewhere), you get a system call failure rather than an OOM kill.
I've found the linux memory system to be far too complicated to understand for quite some time, compared to what's documented in, for example, The Design and Implementation of The FreeBSD Operating System, for a more comprehensible system.
(I’m talking in general here - not Linux specifically)
Everything I'm describing is about a busy server with heterogenous workloads of specific types.
Couldn't the system just reserve the pages for future use by the application but still use them for caching until the application actually tries to use them?
IIUC Linux was really the first OS to make overcommit so prominent. Most systems were a lot more conservative.