Best practices calculated attributes

I have a simple example where I want to show the age of an Employee.

I can easily add a calculated attribute to the Employee entity and let a microflow determine the age, but I understood this microflow will be triggered each time the Employee entity is retrieved somewhere. Although this is not a very heavy operation I still want to know if there are better ways to use attributes like this. We are also planning to use more calculated attributes like informalName, formalName, displayName etc.

I was wondering whether moving the calculated attributes to a separate entity would prevent the microflows from triggering each time. Would it be wise to move them to an ExtendedEmployee entity which would be linked as 1-on-1 or as a specialisation?

Or are there better ways to display calculated attributes like age etc?