Practicing interviewing always seemed to me like studying the day before the exam: if you're lucky and the things you studied actually helped you to pass the exam, you would be lying to yourself because a couple of days/weeks later you won't remember anything of what you just studied. You didn't deserve to pass the exam, but, hey, nobody knows.

Similarly, if you practice an interview and you're lucky enough to being questioned the topics you just practiced and they hire you, what kind of impression are you going to give to your future teammates when some weeks/months later they ask you something related to that topic but you don't remember/know? You just Google it? Well, you can google "how to render a template in Golang", that's fine, but you should not google "what's the difference between a compiled and an interpreted language" because there are some things that you should know before starting to work as a professional software developer.

I know that "the tech interview process is broken", but we, as part of that process, should aim to improve it, not to trick the system for our own and personal benefit.