Definitely. Especially when coming by 12-15 hours is incredibly difficult, for any number of reasons. I often come away with the feeling that for having run this kind of marathon—and that's what it feels like nowadays—I should have managed like a week's worth of work, especially considering, as you say, all the perceived efficiency gains.
But modern high-level tooling and frameworks have their drawbacks, too. One spends an inordinate amount of time figuring out how to do things "the frameworky way". I understand the upsides, of course, but it has still led to a profound frustration with the modern-day practice of programming. Back when I wrote C, I may have had to write 10x as much code, but at least I was churning out lines of code perceptibly. With a small standard library, there wasn't that much to stop and look up. It was an exercise full of "creative flow". Nowadays, I have 27 browser tabs and 5 API references open any time I need to actually do anything, and that in itself can be a major psychological blocker.
As for "procrastination" through "work-days", I don't do that much, maybe an hour of "random rubbish" a day tops. Grabbing lunch is a nice short break; eating it, another; 10 minutes of weights, another; showering, (h)eating dinner, filling/emptying dishwasher.. it all adds up to just the right amount & length of brief brain breaks "aerating" the work day/routine.
The feeling that's worse than any sort of misguided guilt about off time is when you did power through some 12-15 hours and reflect back on & summarize what exactly one has managed to produce net --- it often feels like disturbingly little for the time, given all the high-level tooling, frameworks, helper libs and the fast hardware & internet we all enjoy today.