Is it correct that the timeout set on a task starts from the moment the pod for that task is created (but not necessarily yet scheduled/running)? Because that's what I'm seeing right now

It starts when the node in the dag is running. Let me tag you in another thread

Yes

You can effectively set a runtime timeout by using a pod template to set the active deadline seconds but it’s less user friendly.