What if someone edits the sqlite file via sqlite rather than the config file?
Think of the sqlite database as a "deployed" configuration, not the configuration that you work with. Put together some process documentation for deployment procedures, you'll need it anyway.
What if sqlite3 goes out of business? How will we edit the config files? Where can we purchase sqlite3 support?
sqlite is public domain. And if the support issue can kill your proposal, you should be worrying about where to get mongrel2 support, in case Zed falls off a bike.
So now we can't even invoke the server, we need to invoke some complicated shell script? Sounds like a maintenance nightmare.
Congratulations, you've just introduced a fraction of the complexity in apachectl. Have a cookie.
Mongrel2 makes me feel fear, uncertainty and doubt! These are negative feelings!
I don't know about your manager, but mine would definitely cringe with fear, uncertainty, and doubt upon seeing some scary temporary hexadecimal filename.
Oh, and since we're bikeshedding, might as well point out that Step 3 has a useless use of cat. Grumble, grumble.