An other issue more intrinsic to filters is their inconsistency: because only applicable filters are shown entire categories can be missing and you need to hunt through every time.
And this issue is extremely common IME.
It's one of very few times I'll allow an animation. If the go button has been available but not clicked for some seconds, it will call attention to itself. I hate that but the only users who see it are the confused ones who need it. (Hopefully.)
That is...pick...pick...pick...Go.."No results for your filters". That's not fun either.
I find I use filters - again Home Depot is a good example of bad - because the search is too loose. I'll enter a brand in the search term and have to use filters to pick only the brand I want to see.
The search should first try to answer the users search, not dump more possible products in the customers' face hoping the buy sonething.
A) Added overhead to the backend
B) UX - if you some filters but not the one(s) I want or need, then I'll get frustrated. No filters at all won't set me up for that. For example, eBay's filters are good for some types of products but not others.
C) A and B combined. I've noticed that some filtering UX - Home Depot, I believe is an example - will update the count of the # of products matching your filters. Check a box...wait. Check another box...wait. Fat finger the wrong box...wait...uncheck...wait.
I'm not saying these are reasons to not use filters, only pointing out some friction.