I am still undecided as to whether to keep khttpd in the kernel or not.. it takes up space, isn't perfect, and kftpd is a better solution for most problems.

Here's a wild idea. Dunno if this will work.

I've noticed that if you are using a web browser, and you browse to to a set of HTML files stored on a FTP server, that it will tend to work more or less the same as if you were getting it from a web server. As long as they're plain HTML files without any server-side processing needed, it's almost transparent.

What if you messed around in KFTPD and created some kind of a "Fake" folder that appeared in the root directory which pointed to the necessary pages (which your code would assemble on the fly)?

I don't know if this would be more work than simply using KHTTPD or not, but surely it's got to have a smaller memory footprint if you do it that way?