Actually, have you tried using a class E address? Not all that long ago, even Linux wouldn't permit use of a class E address, although it appears that has been fixed. Given the number of ancient installations of all sorts of operating systems out there, it would not surprise me to find that a non-trivial fraction of internet-facing devices would simply barf if assigned such an address or if instructed to access said address.
As another data point, pinging a class E address from a fully patched Windows XP machine says "Destination specified is invalid." which means Windows up to XP has class E blocked at the network stack level. That means Win2k and previous also have that problem.
Of course, that's not to say we shouldn't fix things so class E space can be used. After all, what's the point of not using it?