I created those setKeys methods because the names are more or less consistent among different analysis (or at least we try), and we end up with lots of code duplication for building those parameter names.
I understand some of those parameters can later be used in (like in the getRStatements()), but i think we cane read that property once set, like this:

{code}
timeVariableConfigurator.setKeys('time')
...
 protected List<String> getRStatements() {
        [
              '''SurvivalCurve.loader(
                input.filename      = 'outputfile',
                concept.time        = '${timeVariableConfigurator.keyForConceptPath}'''',
        ]
    }
{code} 

I think setKeys() not only takes advantage of the current consistency of the params, but also encourages it to expand further as it removes code duplication.