With Pomodoro, I assigned each chapter one "pomodoro" (25-minute time period). At the end of that time, the chapter was done, whether I'd finished it or not. As the timer ticked down, I'd see it out of the corner of my eye and read faster, eventually just skimming the first sentence of each paragraph and maybe soaking in one or two details every couple paragraphs. When each chapter was done, I'd have a rough idea of what the main thrust was, and a fistful of details as well. I'm pretty sure I got a B+ on that book report, but I was just amazed I got it in on time at all.
So in this case, I found it useful as a way to complete a large, boring, segmented task in a quick-and-dirty-but-effective way. I wouldn't recommned it as a cure-all, but it's a good tool to have in your belt for certain kinds of tasks.
I too ended up in a similar situation in university where I needed to complete a large programming project in a single night, and I did it. Now granted, that was a fault of bad time management on my part, but using disciplined programming I was at least able to recover from it and complete the project. And I have had a few instances in the business world that had similar tight and tough deadlines that were NOT a result of time management failure on my part.
If there's a problem with blog posts like this one (and especially so for ebooks) it's that they'll feel a need to justify a cost/article by rambling at length when 5-10 bullet points would suffice. Maybe that's what you're unhappy about.
But the problem is not with discussing or coining a name for a method. Countless 'cutely named' methods have been successful in part because of their names, e.g. Crossfit, 7 Minute Workout, 4 Hour Work Week, Five and Two Diet, Paleo Diet, etc.