I explained my situation above.
Do you have apps like Swipepad that give you an option for a ongoing notification to keep themselves loaded/ always ready to quickly launch? If so, wouldn't you rather accomplish the same thing without cluttering your notifications?
Do you have particular apps that when killed (by the system) in the background result in loss of continuity of their function? For me, this happens sometimes with navfree navigation when I hit home and open another app (even though I am in the middle of getting turn by turn instructions on navfree). Other map apps don't seem susceptible, but I prefer this app and I can make it work...why not do it. I have similar problem occasionally when recording a jog on mytracks my s4 (never had it on my kyocera which I also jog with). The result is the track stops and I need to manually start a new one. Why should I not fix these (navfree and mytrscks) by giving these apps higher priority (always resident) so they run from the moment I launch then to the moment I kill them?
Btw, I have probably 400 apps on my phone. These are the only three that I see fit to assign "always resident". (The tasker notification visible after you pull down the shade might fall in same category...haven't looked closely at tasker settings to see if I can get rid of that and replace it with "always resident"). So I am not taking over android function....just helping steer it on the general right direction fit the few particular apps and situation that it falters. . The results seem good to me and I believe the logic is sound. Would be glad to discuss it you still have some objection.
In the meantime, it might be interesting to know what apps and situation the op is referring to.