great thing about phone interviews is they won't know that you are reading from a script! Writing them and repeating them also helped me memorize them enough for in-person interviews.
It also calms the nerves to feel so well prepared.
At the end of the day, doing a bunch of medium difficulty and some hard difficulty questions on leetcode proved to be the best preparation. By the time you get to your interviews, you've probably seen a variation on what they're asking. I didn't find doing more interviews to be much more helpful than just doing a bunch of practice questions (if you're already good at interviewing in general).
Still, I think this garbage is annoying for senior developer positions or once you're at least a few years out of school. Having to practice implementing a topo-sort in 10 minutes or doing some tedious combinatorial problem gives zero insight into good software engineering practices. System design questions, on the other hand, are actually useful.
Regarding books vs real world practice - I came a lot more confident by going through the process a few times talking to real interviewers. It's not only you and your laptop and zero stress. This make a big difference in boosting your confidence level.
I found out that putting 2 months of preparation reading books, practicing on your own, etc. is not relevant enough. Chances are, you will get questions that aren't directly related to what you've studies. Another thing I found out is that interviewers ask the same coding questions and this happens very often! ta-da!! You know where I'm going?
After a month interviewing, you'll have a chance to think about all the questions you've been asked, then you'll be able to come up with an answer next time. You'll be surprised when you'll start getting the exact same questions over and over. Don't study on your own, involved companies and real interviewers in your practice. Jump straight into the interview process and take a lot of notes ;)