I recall it does, but not sure !
Just cause one Indicator to be attached in the first place, switch it of and now change the number of units (like from 10K to 100K) after you tested how that looks like with the indicator active.

Use CalculateOnLastbars = xxx

You’d say that this influences the visual presentation only, but it doesn’t. Hence this really helps. Try it (and observe that it keeps on doing all the math).

Notice that an indicator as how we use it mostly, is for graphical presentation only anyway; once it’s used (called) in the program code, you can just as well have the indicator code in the program itself and it is faster again.
Exception are the internal indicators which work blastingly fast and which don’t require explicit calling.

Having the parameters is a reason indeed, but that can be replaced by Optimization Parameters.

I suppose areas exist which I did not cover and where it keeps on consuming time which can’t be avoided, but I personally did not run into those. OK, I know of one of them already : a commercial indicator (MarketPlace and such) of which you don’t know the code. You can’t a. have the code in your program code and b. set CalculateOnLastbars because that is set in the indicator itself and you can’t get in there.