Legal teams evaluate licenses and then ban the usage of your software because your attempts to be cute with license clauses pose an unacceptable business risk compared to the value you provide.
If you want your software to be usable, choose standard licenses and don’t modify them. Unless you find value entirely in creating something and not in being useful to others, be extremely careful with creative licensing.
It's useful to others. It's just not useful to enterprises. This may be a positive or a negative depending on your intentions. You can read such a license as a kind of non-commercial use license.
In fact this is exactly the business model of the SQLite project. They have a "cute" public domain declaration and then they sell actual licenses for a fee to enterprises that want to distribute SQLite worldwide.
Copyright holders suing the licensee for a breach. Regardless of if the suit has merit there will be significant legal costs in defending against it and significant engineering costs in replacing the software, often quickly. Likewise there could be image issues for the company violating license terms.
It will deter orgs large enough to be worth suing. It will not deter individuals who click ok on everything without reading nor startups that play fast and loose.
If you want your software to be usable, choose standard licenses and don’t modify them. Unless you find value entirely in creating something and not in being useful to others, be extremely careful with creative licensing.