The spike in the profiler is a bit earlier. The line you have highlighted is only taking 0.07ms which is fine. Total cpu usage at the highlighted line is 1.04ms or 1.84ms which is also fine.
I would look into BehaviorUpdate which is taking 0.71ms if you must ( Which is where all your code is run ), also I think the spike was actual a single frame earlier by the looks of the screenshot, and another larger spike a few frames before that
The things you’re pointing out are part of either the runtime or the engine itself. At a certain point a coroutine has to move to the next yield instruction and a transform has to have a new position applied.
Wow, there are 1000ms in a second. Meaning you have 17ms to play with on each frame to get 60FPS.
Dont bother optimising (to a point) unless you are having issues.
EDIT:
Ignore most things that arent your own scripts. Dont even bother.