OK so this problem has not been resolved but worked-around. I finally saw in this very useful post that I can have anonymous endpointBehavior s. The behaviour is now applied and custom faults are correctly (in a non-standard kind of way) returned as HTTP 200s.
Making the behavior anonymous means it is applied to all endpoints, but as my service currently only needs a single endpoint this works for me.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.