Not really. He was making a pretty serious error of not really understanding the "users," prioritizing his esoteric concerns over arguably more important ones, essentially forcing his users to serve his system instead of building the system for them.
I think a more apropos Ford quote would be the "you can have any color you want, as long as it's black," but that still doesn't capture it.
It's one thing to present something that meets the needs of your customers that they didn't anticipate, it's quite another to ignore those needs and just force the thing you want on them at great cost. He was only concerned with software engineers writing less time conversion logic, and cherry-picking to try to justify that idea. If you think about it, the whole thing is crazy and backwards, given how people use time 99% of the time and who is better at arithmetic.
Maybe sometimes, but it's a different kind of failure when culture is demanded to accept any change imposed on it by some "system."
I can see some value systems where Costa Rica's address system is stupid and unjustifiable (and those value systems are very common among software engineers [1]), but I can also see value systems were it isn't (e.g. ones that value many things that "modernity" discarded in favor of technocracy).
[1] e.g. the value system of a former colleague of mine, who seriously believed that time zones should be abolished in favor of people using UTC for their daily life, mainly so it would be easier to handle time in software systems.