I'm ngl if I see this shit, I just hard power-cycle the machine. I ain't got time for that.

I've never see it, who sets it? I only have two processes that are like it and blth wait for 1:30

Due to what I call some quirks (but what other people call "good, sane, excellent design decisions"), you can set a hard timeout… that can be flatly ignored by systemd for various reasons that might or might not be obvious. In that case it will happily show you <current timer> / <timeout>, then move to <current timer> / <timeout * 2>, and so on.

Because that, for some reasons, makes a lot of sense to some people that are not me.

Just set the limit to something sane like 2³² seconds!

This is the way.