I don’t think that these limits have ever been enforced by any version of Windows. They have always been hints that the OS uses to help decide what to do. Letting any UM process set hard limits on what a virtual memory OS can do is an incompatible design philosophy. I don’t think that even VirtualLock has ever actually worked exactly as advertised, but I have not looked into this in a long time
The better question is why you care? Even if the limits did work, there is no way to control which pages are paged in or out. If you really want resident memory, then large pages are a much better choice, and if you want to limit the resources used by one process, then the only reason would be so that another process gets a chance - something that memory manager is in a better position to control anyways.