No, not really. Engines are super lightweight data-wise. And having dozens of them does not break the game (IDK about hundreds though). AND testing sorta IS about breaking the game, finding ways to do that is precisely the point. I work as a tester (no, not for Automation) so I know sth about that.
@DuceTheTruth100 As for just naming, I think there once was a similar thread 
Aha, found it: Best company/model/trim/engine naming/labelling system (ideas)
There is my post about that too. In short - I prefer to use some systems, more or less elaborate, as I like them, but for some testing, experimental, temporary or uncertain engines I just use desriptive names (well, descriptive to me).
Oh, and as for cloning - choose the “trim + variant” option, not “trim only”, and you’ll have a separate variant for the update.