You only gave me two options :) First, I am doing this because I am curious. I first looked at the 451 error code for a publisher many years ago where we were

You only gave me two options :) First, I am doing this because I am curious. I first looked at the 451 error code for a publisher many years ago where we were anticipating a court order banning an article in a given country. Second, I have a number of sites where we have done the work to be compliant with GDPR so thats nice. Third, there are sites where there is so many third-party scripts added over the years that it would take months to administratively figure out what is needed and what is not. They were not just added on the template level (medium/easy to clean-up) but added by individuals directly through a CMS which makes it very very hard. Its in that third case that we might be forced to have our own 451 error page (or something else) until it can be untangled. I'm an advocate of the GDPR and welcome its challenges but its technically difficult even if you mean well. I'm sympathetic to those hitting problems. To be clear, it is NOT about 'choosing to comply' or not, and saying so means you don't fully understand the technical challenges.