Yeah, it kicks your ass when you're just getting started and helps you move somewhat quicker once you have experience. But I have observed what you point out many times. I'm not sure it's worth it, in the end. You learn how to Google error messages, that's for sure.
Haskell: favor composition over configuration over convention.
It works well for JS, too. Favor function composition & higher order functions for code reuse over complicated prototype hierarchies.
function composition in js can be tricky to visually parse the "types" (especially if curried).
It depends on the return value, yes. I usually try to keep modules small and use some kind of threading (needle + thread analogy, not os threads/web workers) strategy when building functions -- pulling out common patterns into globally visible utility functions that work with common types (e.g. jQuery events/objects).
It's not ideal, but in the absence of a true type system, it's all about mitigating potential problem areas.