Keeping this path in the database would allow for a header image directory such as .../wp-content/header_images. Then upgrades could pick up the path from the database and manual upgrades would be half the work they are now where we need to copy everything out of old_theme/images/header into new_theme/images/header.
I'm not suggesting changing the default path, just adding a persistent overload capability.
I've faked this with a single static image using the new header image HTML in 3.6.4, but putting it in the db would:
- Keep the existing Header Image tab functionality
- Avoid rendering a hidden header image behind the new one
- Eliminate messing with the contents of theme's default header image folder
Thanks! BFA Rocks!
-- Richard