That's an interesting idea, but as someone else pointed using a voice modulator would be much better. Technical skills are importants, but human behaviors too. I would not trade a nice average coworker for someone who is better technically but doesn't know how to communicate. And typing is complementary, not a replacement for voice communication since the amont of information you can share in a minute is 3-5 times higher by voice.

This is interesting. Don't have an opinion on it yet.

I wonder what effect this will have on developers' code reuse practices and how it comes across in the interview.

At work I often look at my previous work for how to do boilerplate stuff. And in my recent interview experience I had more opportunities to use the internet and other examples. Very practical

The typing only thing is a bit unfortunate. There are enough voice modulators out there that they could probably pay for. V-tubers do it all the time. I don't really care about the voice, just that they can speak the language properly.

What would be great for interviews in pair programming and working on a solution to some realistic thing e.g take an opensource repo that solved a problem and work together with the person to try and resolve it. You could also put them in mock situations where they have to resolve a disagreement about something e.g how something should be documented, or reason about why a subpar solution has to stay in place, etc.

Just do something that would actually happen at work instead of these "how would you implement a linked list" or "implement a b-tree" or "please take this personality test before we can have a technical interview"...