"We can't serve you this because our jurisdiction forbids it" seems likely to arise more often.
That said, I also don't think the 4xx/5xx distinction matters as much here as the evocative implication of using 451 specifically.
Uh, it happens all the time. In fact, it's by far the most frequent kind of censorship.
From TFA:
- https://en.wikipedia.org/wiki/Censorship_of_Facebook
- https://en.wikipedia.org/wiki/Censorship_by_Google
- https://en.wikipedia.org/wiki/Censorship_of_Twitter
Most major web services are based in a country with relatively lax censorship laws but still comply with censorship laws in other jurisdictions.
What is a good use case for HTTP 451 then?
Rarely does the calculus favor getting your entire site blocked because you refuse to censor one piece of content. At least by serving HTTP 451 you could also potentially offer suggestions like using Tor.
This is because censorship is almost never global—instead, it's because something about your request (often, your country of origin) forbids you from receiving it.
In that context, 451 makes perfect sense.