Strong arming Elon's intentions, may be he is used to perhaps how code reviews work in Space industry? Sometimes old school ways are fine, under the hood it is just code.
It is simply much quicker and much more efficient to do something like a proper code share in an office with one person driving the code and being able to jump between areas of the code.
To say it bluntly: Anyone that uses printed code for code reviews is wrong. It assumes all functionality is colocated and nearby. It wastes time by forcing people to index through multiple pages of paper. Anyone that demands it should see prompt pushback.
We did have very thorough design documents and manuals and all of them have been printed (including documented function headers) as the contract dictated, but we only used the original word documents and the version control system to review our code.
If I'm forced to print code, I would probably do it. It is essentially a few clicks taking a few minutes of my time.
On the other hand, your tech lead reviewing code on paper is going to be extremely painful. The tech lead who is forced to review code on paper would probably quit first.