[OnePlus 2 Android Development] return.of.octobot:
So, I'm not sure what you're using to tune, but regardless, if your issue is disabling touch boost, add this line to your init.script or manually change the indicated parameter to 0 using a file manager:

##DISABLE_TOUCHBOOST##

echo 0 > sys/module/msm_performance/parameters/touchboost

Otherwise, if this better answers your question, I constructed the following script to keep the frequencies themselves in check. Obviously you'd need to change the values to suit your needs:

##A53_MINFREQ##

echo 384000 > sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 384000 > sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 384000 > sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq
echo 384000 > sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq
echo 384000 > sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq_hardlimit
echo 384000 > sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq_hardlimit
echo 384000 > sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq_hardlimit
echo 384000 > sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq_hardlimit

##A57_MINFREQ##

echo 384000 > sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq
echo 384000 > sys/devices/system/cpu/cpu5/cpufreq/scaling_min_freq
echo 384000 > sys/devices/system/cpu/cpu6/cpufreq/scaling_min_freq
echo 384000 > sys/devices/system/cpu/cpu7/cpufreq/scaling_min_freq
echo 384000 > sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq_hardlimit
echo 384000 > sys/devices/system/cpu/cpu5/cpufreq/scaling_min_freq_hardlimit
echo 384000 > sys/devices/system/cpu/cpu6/cpufreq/scaling_min_freq_hardlimit
echo 384000 > sys/devices/system/cpu/cpu7/cpufreq/scaling_min_freq_hardlimit

##A53_MAXFREQ##

echo 1632000 > sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1632000 > sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
echo 1632000 > sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq
echo 1632000 > sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq
echo 1632000 > sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq_hardlimit
echo 1632000 > sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq_hardlimit
echo 1632000 > sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq_hardlimit
echo 1632000 > sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq_hardlimit

##A57_MAXFREQ##

echo 1632000 > sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq
echo 1632000 > sys/devices/system/cpu/cpu5/cpufreq/scaling_max_freq
echo 1632000 > sys/devices/system/cpu/cpu6/cpufreq/scaling_max_freq
echo 1632000 > sys/devices/system/cpu/cpu7/cpufreq/scaling_max_freq
echo 1632000 > sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq_hardlimit
echo 1632000 > sys/devices/system/cpu/cpu5/cpufreq/scaling_max_freq_hardlimit
echo 1632000 > sys/devices/system/cpu/cpu6/cpufreq/scaling_max_freq_hardlimit
echo 1632000 > sys/devices/system/cpu/cpu7/cpufreq/scaling_max_freq_hardlimit

So while I unfortunately cannot answer this question, I would like to add that typically selected A57 governors also revert and/or change to match the A53 governor after cluster shutdown, e.g:

A53: Smartmax, A57: Darkness > *A57 SHUTDOWN* > A53: Smartmax, A57: Smartmax

Also, despite having implemented init.d to set my chosen governors and parameters on boot, sometime between when the script (Preceded by 99) is run and boot is completed, they revert back to Interactive. They rest of the parameters defined via init.d remain intact, so what I find myself having to do is manually run my init.d script after boot finishes to reset governor parameters to my liking.

Sent from my Tℹ?$Y ONE A2005