In order for a PHP script to be able to change any file, the process running trhe PHP script needs to have read/write access to the file.
If you want users to be able to change the httpd.conf file from your web pages, then the httpd.conf file needs to be editable by your web server process user - possibly apache or nobody.
In order for the changes to take effect, this process would also need permission to stop and start your apache instance.
But are you really, really sure you want to do this?
If you set things up like this, it means that you are completely reliant on your application level security. If an attacker breaches your security, you are allowing them to control how your apache responds to requests. The attacker could reset your apache to:
display php files instead of processing them - thereby exposing database connection details etc
silently route visitors to a bogus site
remove .htaccess protection form any protected directories
and all kinds of Very Bad Things