Unexpected behavior in Autofixture when customizing booleans

I understand that AutoFixture has a strategy how booleans are created (starting at boolean value true). At least there seams to be a pattern:

AutoFixture .With vs direct assignment after

In our code base, we have places where people do