Thanks boldbeast for trying to figure this out. I can confirm the SELinux mode is set to "permissive". I did three tests to verify this.
1. I installed SELinux status check app and it confirmed that I am already in permissive mode.
2. I installed Viper4Android driver which requires SELinux to be permissive for audio driver to finish installing successfully. I was able to install it fine on SELinux permissive Kernel and it did fail on stock kernel which has SELinux permissive.
3. Verified with custom kernel developer that he has SELinux configured as permissive when he compiled this Kernel.
The insufficient permissions issue you are seeing with boldbeast, could it be due to it unable to get permission to VOICE_CALL parameter due to Samsung limiting access to this parameter only to System apps that are signed by the platform/ROM keys from Stock ROM and Boldbeast's APK is signed by different keys?