They may not have "a mental model of statically typed languages," but they sure "agonize" when there are eight different incompatible datatypes that represent a datetime and the library functions they want to use don't even specify which of these they take or return.
It's true that compulsory static typing can mitigate documentation bugs. But the effect isn't significant in the programming beginner experience.
They might not "agonize over variable types," but they do encounter agony when they try to add a string to an integer.
Yes. But statically associating types to binding names does not relieve them of making and fixing these mistakes, it just makes it a runtime vs compile time error.