Yes, replaceable components could be used for that. If you put:
replaceable ParameterSets.Records.Set1 set
Then as before you can add choices for the user in the annotation. You can either add a choice like this:
choice(redeclare ParameterSets.Records.Set1 set(m=2,c=2,f=2) "Set 2")
Where you directly in the annotation hard code the different values.
For scale up, I would suggest using this instead:
choices(choice(redeclare ParameterSets.Records.Set1 set "Set 1"),choice(redeclare ParameterSets.Records.Set2 set "Set 2"),choice(redeclare ParameterSets.Records.Set2Alt set "Set 2 alternative"))
Now the actual values can be changed in the records instead and it is easier to add new ones.
You need to create a base class with this replaceable component. In an extended class, you can choose to redeclare the record:



I updated the model file and attached it below!
Attachments: