Should the isUUID default be ‘loose’ by default to undo the breaking change from #2421 before the new release lands?

Personally, I don't agree with that. I see where you are coming from, and that the previous release could be considered a breaking change. Currently I do not see the need to change the default behaviour, and with this release we give people that had issues with the current release another way to deal with UUIDs.