Most systems (maybe 70% today) couldn't reach it, it's harder to estimate how many _people_ because people may have many options to access the Network and some are more likely than others to be IPv6 enabled.
It also varies geographically, in some places (e.g. Germany) it may be about half of people who have IPv6 access, in say Australia it might be more like a quarter and so 75% could not reach that site.
As we see above in this HN thread some users intentionally disable IPv6.
If I were to remove cloudflare, more than 30% of users can connect to the site via IPv6. Problem is that other 70% will consider the site dead and move on.
But I can't send anything to such a user directly if they don't support IPv6 and I don't have an IPv4 address.
Perhaps we need some community-run webservice with an explanatory page saying "Website [something.com] requires IPv6, here's lots of documentation on how to try and fix this" and everyone could point their domain name IPv4 address to that webservice, and the IPv6 address to the real server.
For hobby projects hosted on a Raspberry Pi in someone’s bedroom, I can imagine a static IPv4 being prohibitively expensive, but that’s about it.
What you're probably going to see is increasing cost to keep a dedicated public IPv4 address. If you don't, you will probably either have to have IPv6 or NAT.
Residential will probably lose public IPv4 addresses faster than for hosting services.