I looked at 2ndinit at github and I have a question.
You are using some code from phh's SuperUser to disable SELinux of init, ueventd, recovery and the shell from recovery. My question is, can this code be applied to get a full SELinux Permissive at boot? Just wondering cause we are trying to boot custom ROM on it and well, locked bootloader has his limitations...
I was about to pick up a commit from ggow (netd binary that loads at boot from init.rc) that injects some code to netd to disable SELinux at boot but the commit is gone. Will your 2ndinit help to get a full permissive SELinux at boot? It can be a good option since it runs directly after mount the system (ext4_resize).
Cheers and sorry for the OT.
Possibly. You can try calling setenforce after you've disabled it for init.