I imagined executable pages and pages explicitly marked by the application/kernel via VirtualProtect[1] or similar.

Of course an application that marks GB of data this way could play havoc with other processes, so maybe some OS limits on how many non-executable pages a process can mark may be needed.

And there certainly might be some further dragons I'm not considering.

[1]: https://learn.microsoft.com/en-us/windows/win32/api/memoryap...