If a solution would have been found more quickly had the developer engaged their colleagues for help or advice, they cost the organization by wasting time trying to be a "rock star" instead of a team player. They would receive coaching to discourage that sort of counterproductive behavior in the future.

Maybe. But then you eat the time of those 1-2 other people by interrupting them, giving them the context of what you're working on, etc.

My guess is it's a net loss for the org in most cases. The exception being if you sit there for days.

Hah well that was my presumption. Obviously balking the minute you're stymied is silly, too.

My objection is with never asking for help, not trying for a while and then looking for help only after you've put in a reasonable effort.

Seems like common sense but you know how common that is... :)

Agreed :).