Memory safe languages are ultimately built upon an unsafe foundation.
Why? Do you not know how to perform a specific task within functional code?
In which case, you should probably take that opportunity to find out how to do it.
It's not that I didn't know, it's that the process was imperative at its core. For example, I am working on a rendering engine using OpenGL. The high-level scene graph interface is purely functional, but rendering such a scene graph is an imperative process: binding textures, vertex arrays, shaders, writing to a framebuffer, etc. This low-level rendering code is the functional runtime for the high-level API.
You could do that within a purely functional language (via monads), but given how locked to C and the imperative paradigm OpenGL is, it would make sense to simply write that in C, yes.
Not necessarily. Functional language compilers are very sophisticated and do not necessarily compile code the way you might think.
If you use an abstraction (your job as a programmer) the innards of the processor should approach inconsequential.
For the record, I prefer purely functional programming, but it's not the only tool in the tool box.
It is, but the code barely resembles the code most imperative programmers would write.