Maybe it means that current design is poor. However since this behavior is documented there are users who might depend on it. So I doubt it will be changed any time soon.
Though I wonder maybe we should consider introducing a new set of time-related procedures with different behavior (to_timestamp_strict?), that would be more obvious to users.