What are the considerations of enabling and disabling the global "SQL Pruning" setting in BIP?

A customer enabled the global SQL pruning setting in production which caused various BI publisher report issues (primarily, missing columns from various CSV and RTF outputs). The setting was ultimately reverted back to to the default "False" setting, which appears to have resolved all of the "missing column"-based issues, however we are noticing some other strange report output issues now such as date/time formatting changing or other missing elements from BIP reports that were only noticed after this setting was changed, and are still causing problems.

We are trying to understand if the setting change had other unintended consequences and more broadly, to understand what the implications, considerations and any known issues are around changing this global setting (and ultimately reverting it). Is it expected that certain data model or report issues may linger? Do we need to request a bounce of the BI server?