Reloading apache will cause for a log file to stay open, since the process never exited, only re-read the configuration file.
You can either change the logrotate to copytruncate or use different type of logging inside apache configuration (pipe to log program e.g logger).
Third option is to issue an actual restart, not reload, which will force apache the recreate the file after restart, if you can have a bit downtime.
I do not see a problem with editing http configuration files to change way logging is done to suit your needs.
Whatever you do, a reload is not a restart, so apache will keep the log file(s) open and write to those files.
This is if you use logrotate to rotate those logs without apache restart or copytruncate option.