palto42 Of the settings you list, my experience of TLP on my laptop suggested that:
TLP_DEFAULT_MODE=AC
Gets overridden by the device's reported power mode. I can't think of a situation where the default would be applied on a laptop.
CPU_SCALING_GOVERNOR_ON_AC=performance
CPU_SCALING_GOVERNOR_ON_BAT=schedutil
These were overridden by the built-in "ondemand" governor, which performed better than the Solus TLP default governors when manually-enabled. As they were disabled on my system, there was no detrimental effect from the Solus TLP defaults.
CPU_BOOST_ON_AC=1
CPU_BOOST_ON_BAT=0
This did as promised and prevented the CPU from boosting above its base clock rate, even on a 1.6GHz Celeron. Anecdotally I found this extended battery life slightly, at the cost of a less-responsive system. On a more powerful system the downside may not be noticeable.
RADEON_DPM_STATE_ON_AC=performance
RADEON_DPM_STATE_ON_BAT=battery
I wasn't able to test these, but the Solus defaults appear to favour battery life when on battery power, which seems reasonable.
WIFI_PWR_ON_AC=off
WIFI_PWR_ON_BAT=off
SOUND_POWER_SAVE_ON_AC=0
SOUND_POWER_SAVE_ON_BAT=0
USB_AUTOSUSPEND=0
I didn't try these but expect the reason they are disabled may be compatibility, rather than performance-based. Notably I am unable to test for broad hardware (in)compatibility. I can't imagine sound power saving would have much impact without a dedicated sound card, and WiFi power saving may not be a desirable feature nowadays. However, the performance difference may be worth testing.
Do you think there could be a noticeable performance (battery life) gain from changing any of these settings? Or might there be other advantages to adopting the standard TLP default config, such as faster updates? If not, then the potential for incompatibility with undefined hardware seems a fair reason to stick with the status quo.
