'Repeated property access of built in component is inefficient' for Property setters is pointless

In this context there is no point in showing this warning, due to how Unity handles CharacterControllers (and NavMeshAgents) positions they need to be disabled before changing their position and then re-enabled afterwards meaning this is perfectly valid code but Rider assumes some inefficiency here.

No repository file or test is named. Start by reproducing the warning in Rider with Unity CharacterControllers or NavMeshAgents whose positions are changed while disabled, then locate the inspection responsible for repeated built-in component property access. Done means the warning is no longer shown for these valid property-setter patterns.

Written by the indexing model from the issue text.