I think the question I would raise would be 'Do you want to get rid of http?' Are you intending this perld to be a web app server? If not, then I can understand your idea. Apache handles HTML, SSI, and various script handlers, of which mod_perl is one.

If you are just executing (non-web) perl applications, then forcing perl to remain resident might perhaps be a good idea. However, consider that your operating system and processor are already caching libraries and apps (including Perl) that are executed frequently. If your daemon is not running anything, then it, too, runs the risk of being virtualized into swap space.

I would suggest that you spend some brain cycles considering how your (non-Doze) OS can be your friend. It already has prioritized schedulers, memory management, time-based program execution, and an in-memory daemon called the kernel. :D