To be honest, no - speed of delivery has actually been pretty good in 1.5.x. From a rough look at the steamdb timestamps yesterday, a third of 1.5.x releases have cleared beta in 14/15 days; another third in 19-21 days; one took three and a half weeks, another six weeks (including holiday season), and then came 1.5.8.
TW's delivery problems* have always seemed to be in code branching/merging / version control / build/package quality. The admission last week that some bugs weren't reproduced on internal builds as on Steam builds wasn't a surprise, but should highlight a flaw in their processes. I vaguely remember talking about this last summer, too - it might even be an area of development that is negatively impacted by disrupted work patterns/working from home more (if they still are). Disappearing textures and commonly recurring bugs all point to build/code merging issues - quality control. People regularly ask why TW testers aren't picking stuff up; they won't if the issues don't appear in internal builds and no one tests Steam builds - so the build process needs improving, and someone at TW needs to be validating Steam builds. Arguably, improving that process might need to slow down the delivery cycle a little, to add in a Steam build test/validation phase.
*they might also have some design/management issues, but that's more subjective and we don't necessarily know their vision.