Perhaps the word "sprint" translates primarily to "short distance" in your mind, but I suspect if that's the case you are unusual in that regard, and most people think of the defining characteristic of "sprint" as "moving fast", not "short distance". To suggest that the choice of that word does not imply a sense of urgency and moving quickly seems, to me, totally implausible on its face.

> And no, developers are not expected to be "in a sprint more or less at all times"

Again, perhaps this is your experience. In my experience, in every company I've worked for that uses sprints, the end of one sprint is separated from the start of the next by, at best, a few hours, and often less than that. Planning meetings generally take place during sprints.

And to point out that sprints may be separated by a weekend seems, at best, totally irrelevant, as in my working life, weekends are not part of working time. "You are in a constant sprint at work, but hey, you get to rest at the weekend" is not a compelling proposition to me.