As for your last point, I'd personally substitute "intuitively obvious" for "surprisingly", but I will admit I've been playing this game on and off for a long time
Why is the relationship between OTPs and Javascript crypto (apart from them being routine signifiers of crank cryptography) intuitive to you?
OPTs obviously devolve to the key distribution problem.
The environment of client side Javascript is obviously to me a superset of the key distribution problem. After all, you start out by distributing your code to the (insert your favorite derogatives here) client.
Simson Garfinkel likes to refer to the whole https game as something like transferring a valuable from a cardboard box in an alley via an armored car to a park bench. I'd end with the end of a Matt Groening Love is Hell quote: "At night, the ice weasels come."
Unless you have a physically secure channel to distribute keys (in which case, why bother with OTPs), the fact that OTPs move the security model entirely to "key distribution" is an academic point. Any online key distribution system you'd come up with for your OTP is (a) going to become the fulcrum of your entire system, and (b) by nature of feeding an OTP, going to permit a far more restricted set of designs than any key distribution system for a "conventional" protocol.
The reality is, OTPs are entirely unsuitable for commercial information security. That's a strong claim, but not a slippery one, and I'm willing to back it up.
The arguments around OTPs are surprisingly isomorphic to the arguments around Javascript crypto.