Constraining unconstrained integer in record on use
I'm not aware of any way to "post-constrain" an integer like that.  

However, in my experience, the synthesis tools will take note of the source of the data that you write to any integer down the line (presumably irrespective of whether the integer is in a record or not, but I haven't tried it) and propagate any constraints from that source onto the destination.