I think my initial reaction is a partial "No," for the reason stated above: the input colors, the colors in Celestia's surface texture image files, are not supposed to be artistically balanced. They're supposed to be accurate representations of scientific data.
("Supposed to" but probably aren't by the time they make it into most Addons, especially if they use jpeg or compressed dds
)
For reflective objects, could one encode a color profile which says "Only do those color transforms required to represent lighting from sources that are different colors"?
For light emitting objects, could one encode a color profile which says "Only do those color transforms required to represent loss of intensity due to distance or obscuring materials"?
To put it another way, I am assuming a "scientific" color balance is maintained and used for all of the images provided for use with Celestia. I.e. the original images acquired from professional astronomical image repositories must be assumed to have an appropriate color balance. (Although, of course, most astronomical sites do not document the image color transforms used for the images on their oureach sites. You have to get the original FITS image files from their scientific database servers, which usually do include documentation about the profile of the frequency bandwidths represented in the image.)
To me, this means that the color balancing problem is an output issue, specific to each system, and not necessarily something that Celestia should be expected to handle.
Each individual display and printer requires its own color balance configuration to ensure that it accurately presents the input texture map image colors to the viewer.
However, this does require everyone's screens and printers to be calibrated with appropriate output color profiles, so that everyone sees the same representation of the colors that were provided. This suggests to me that a procedure or software package for calibrating screens and printers to create those output profiles would be very helpful.