If its still ok to make a big API change, then I think that would be a great idea. And if CSVStrategy is immutable then there would be no need to ever copy a CSVStrategy (so the clone method could go away and a copy constructor would not have to be added).
If that change is made, then it might be nice to use the Builder pattern and get rid of all the normal constructors. That would keep it from loosing the flexibility that the mutable version had and it also makes it possible to add new values to CSVStrategy in the future without having to add more constructors. And I think it would make it easier to tell what parameter each each value goes with (especially with so many boolean variables).
I attached a patch that includes these changes. Surprisingly, there weren't that many changes needed to the rest of the classes. A deprecated constructor in CSVParser needed to be changed to use a CSVStrategy.Builder and a few of the CSVParser test cases needed similar changes. I also got rid of the CSVParser test cases for the getters/setters of the CSVStrategy methods, but I suppose they could be modified to test the Builder inetead.