All FLASH devices have an erase limit before the sector becomes non-eraseable, likely it was not a bad controller but bad choice of filesystem or bad application behaviour that was causing excessive wear in a small location.

With the right access pattern we could hit it at 80kb/sec distributed writes for six hours on an SD card with a wear leveling FTL, which shouldn't be possible. We confirmed with the vendor that it was a controller bug where the FTL was losing track of a virt to physical sector mapping.

Also Flash isn't an acronym and shouldn't be capitalized like that.

How likely is that if you have cards from different vendors?

Are you shipping a product or dealing with a fleet? You don't want two different items on your BoM just because you don't trust the vendor to actually ship a usable product.