Ive thought about something similar too. As calculating texture values uses a window of some size, I assume you had it in mind that the segment would be the window? I suppose a limitation to this would be the window size. I assume the window size always has to be odd? Also it raises questions over the validity of the texture analyses if it is composed of lots of different window (segment) sizes. This would hold especially true if your segmentation was based on optical data but you were populating the RAT with texture derived from radar imagery. Alternatively, you could create the textural parameters yourself (using bandmath), but then populating it into the RAT using the mean may not be statistically accurate? For instance, generating a mean filter and then populating a RAT using the mean would not necessarily be correct.
Maybe an option to calculate a user defined calculation would be more beneficial? For instance the 'populateImageStats' command has no option for range, but you could write this easily yourself using 'max(pixelsWithinSegs) - min(pixelsWithinSegs)'. This could be based on the mu parser library or just python/numpy.
Its definitely an interesting idea.
Nathan