https://bugs.winehq.org/show_bug.cgi?id=47883
--- Comment #2 from Shmerl shtetldik@gmail.com --- (In reply to Austin English from comment #1)
How does it behave on Windows?
Good question, I haven't test it personally. But it's quite possible that due to different underlying libraries and different allocations, on Windows the same program won't run out of virtual memory limit for 32-bit.
Another common case is for example using d9vk instead of wined3d. The former might run out of RAM faster due to doing different allocations for Vulkan use case. Since authors of such games didn't anticipate all these cases, they didn't flip that LAA flag on the binary. Doing it with a patcher is a fix, but the point is to have a a simpler option to force such behavior regardless of the flag. It would provide an easy to access workaround.