It is possible to make cheats as long as nothing took up the debugger slot. If you don't see the by now familiar
View attachment 418813
This message is actually not accurate. When dmnt is not attached to game and the debugger slot is available edizon se would attached to the game directly and you can hack it as usual just no cheat code can run when dmnt is not attached. You see this message only when edizon se cannot attached to the game as a debugger ( probably due to the slot already taken ). I wrote those lines before I added the ability to attach edizon se directly and never went back to change the message. Also if edizon se is not able to attach, noexs also can't as edizon se used the same method noexs attach to game.
You see a screen like this when edizon se is attached directly. The cheat code panel is gone but the rest works as usual. You see the (dmnt not attached) next to the version number
View attachment 418814
Assuming the game is using a loadable module to run the game code, you can make pointer code just that it is more troublesome cause the pointer search don't know when to stop so some manual work needs to be done. World war Z was the first one I came accross and there were a few others that I don't remember the name of. They are rare. The loadable module's main will be labeled base as it isn't main or heap. Base is mostly meaning less, it covers the range from 0 to 0x8000000000. That is everything.
Breeze will tell you the type of memory when you view it with memory explorer. You can do pointer search just fine with Breeze with just a few more extra steps. ( that is for loadable module, Breeze needs dmnt to be attached, when the debugger slot is taken there is no service )