While falsehood lists that cover emails, phone numbers or CSV files are basically just a much better specification than the one you were following initially, this falsehood list works on a different level. You can't simply go through all the items and make sure your code covers each one. You're supposed to read it and come to a conclusion that economics is less similar to mathematics and more similar to sociology. That it's not a set of rational rules but something inherently more complex and chaotic.
It can still have a huge effect on your code - not in the form of additional corner cases you need to cover, but as questions you may ask yourself about the purpose and morality of your work. At least that's how I understand it.
The phone number example they gave works very well for demonstrating misconceptions. Economics doesn't work as well for that, for precisely the reason you stated about it being partly sociological. In fact it's sociopolitical, which complicates matters further.
Falsehoods about phone numbers was recently on HN [0], and I liked how it came with examples. Then it's possible to have a meaningful discussion about each one, and if it is something we need to handle. For instance Phone numbers are always written in ASCII, gives an example where that isn't true. Then we can discuss if that case is meaningful for us to support or not.
I cannot build a system that will handle all possible names, emails, addresses, timesystems, currencies, locales or whatnot there is a falsehood article about. So when writing an article like this, if you want it to have impact please explain the point of each bullet.
[0]: https://news.ycombinator.com/item?id=19214035