Quite easy to reproduce:
Set a workflow (different than the ones you used for generating that profile), display it from the library and and saved it.
Many infos are different from the one you saved at generation time. To give an idea here a screenshot of the differences:


Comments:
1. I have noted that generating reports: I am used adding notes in profiles for having then shown in the profile. Off course I have not taken care of the different WF I had used.
2. Even if I had taken care of that, it would not be enough, as, in the meantime I could have modified something affecting the WF. To be sure I display (and save) what I have used in generation, I should save the relevant WF.
3. Anyhow, opening a profile for displaying, it is very unexpected its header is modified, unless, of course, you do operations on measured data. Following that approach I cannot be sure of the settings I have used for generating it.
4. I have verified that the copy (done by accessing the item for modifying it and save it with a different name) does not modify anything in the profile header (a part the name), as expected.

Every time a profile is saved/re-saved, the present ColourSpace setting will be obviously be saved.
This is exactly as it should be.

Steve

But also the display overlaps a lot of piece of info that is relevant to the measurement. They can be retrieved only through the report.
I miss that and a way to add/modify notes without affecting the report.
Any way to achieve that?

That would be a WIBNI, not a bug.
Although I do not understand what you mean by 'overlaps'.

Steve

I think "overwrites" is the right term.
Have a look to my screenshot: the value of Stabilisation Enabled has been changed, as it is saved is what has been latched in the current workflow, Specifically, for the example I have shown, I have started using a WF defined for the Virtual Probe measurements, without stabilisation to make simulated readings faster

Yes, as said, every time you Save a profile, the preset ColourSpace settings are saved into it.
That is as it should be, and is as expected.

We will add a WIBNI for an option to not save the changes.

Steve