The sad part about those exit nodes is that they don't know about where they can't go and if they don't know they can't tell clients in advance that there exit will be not working for them.

Since the ISP is messing with the traffic, e.g. showing a website that tells one an error occurred or that they are indeed blocking the destination those nodes would get the BadExit flag as it is irrelevant who is messing with the traffic.

BadExit's will not be used as exits.

Arguably the nodes would be relevant for some people, but exits are supposed to be useful for anyone, unless the exit policy excludes ports or destinations.

The sad part about those exit nodes is that they don't know about where they can't go and if they don't know they can't tell clients in advance that there exit will be not working for them.

Since the ISP is messing with the traffic, e.g. showing a website that tells one an error occurred or that they are indeed blocking the destination those nodes would get the BadExit flag as it is irrelevant who is messing with the traffic.

BadExit's will not be used as exits. This, not for human intended, protocol shows all BadExits. Luckily there's a list for humans provided via Globe.

Arguably the nodes would be relevant for some people, but exits are supposed to be useful for anyone, unless the exit policy excludes ports or destinations.