That doesn't follow. Lispians have known since the '60s, and everyone else has known since the '80s, that human beings suck at memory allocation, so modern programming languages don't let human beings anywhere near it. You can write anything you want, but there's no way we'd add it to the language or the (official) libraries.
i think #1 is theoretically possible but very unlikely it will be implemented. for that to work, snap code would need to be compiled to GLSL which is a language that is statically typed and does not support recursion. also, it wouldn't be able to access variables/data outside the "warp" whenever it wanted to, because those live in a separate component of the computer.
Computers store data by first, creating a key that says where the data is and then storing it. What you can do is create a key and not put anything where the key goes. It would be a memory hog in some situations but since there is nothing in the slot your computer doesn't have to process it.
#2 Browsers try to use as little memory as possible so if you have a RAM-heavy project there will be lots of lag spikes while your computer is trying to move everything around. This reserves extra memory to try and reduce that. Mainly it's something I would use because my program is running a function for every pixel on the screen and storing the data, so it would be handy if it could just store the data instead of finding a place for it to go.
#1 While theoretically possible, a dev responded and said basically that humans aren't that good at figuring out what processors should run our code so it's better if we let the computer handle it.