I've gotten many code review comments to the effect of "can you break this out into an interface?" so I 100% understand what you're saying.

Many of the instances were things that we were only likely to make one example of either. I could see that argument being valid if there was a clear second implementation in mind, but an interface with only one implementing class is often just wasted time.