SDKCall definitely isn't going to set memory executable, but at least some of a plugin's memory is necessarily going to be. Perhaps it all is, but I didn't check the VM code. I assume the example in the first post works, which would indicate it is (whether intentional or not).