Yeah, so far this is my experience:That reminds me I need to actually pretty-print those results lol. Anything where mod is 349 means it's a Noexs error.
See this for reference:
https://github.com/mdbell/Noexes/blob/master/server/source/noexs/include/errors.h#L8
Oh and Noexs originally was a port of TCPGecko, just after we had about half of it working we realized there is too much different between the Wii(U) and the switch. Wound up being easier to just start over from scratch.
Scan PIDs and attach to process: works
Search HEAP for Known value: Game pauses and proceeds to dump 3GB at 3-4 MB/s, so it takes roughly 20 minutes for the scan to finish.
After scan results appear: Game did not resume. When pressing Run game get error "Unable to resume".
Detach from PID and game resumes. Re-attach and game auto pauses again.
Changed value in-game while detached, re-attached and ran comparison search: expected results found.
Since game will not resume while attached I cannot test poking or locking the value.
At this point the Switch fell asleep and would not wake. Forced restart needed.
From what I've seen though this has great potential. Will post more as I manage to test more out.