How to avoid lag of servo motor used with distance sensor in FRDM-KL25Z
You have several things going on, all of which contribute to your problems:


The "micro servo SG90" is not one of the strongest servos around.  It might not be capable of rapidly swinging the mass of your ultrasound sensor around.
Your code generates the servo pulses in software with a "wait."  When you have only your "sweep" code, it moves smoothly because you are generating pulses all the time at a steady rate.  When you put your distance measuring code in there, though, you aren't generating any pulses while you are measuring distances.  The servo has no pulse - they can hold position or wander when there's no pulse.  Yours probably wanders when there's no pulse.
You are measuring distances at each servo position.  Each measurement takes some time. Your code expects each measurement can take over 30 milliseconds.  If there's nothing close to your sensor, then you will be waiting at least 30 milliseconds at each position.  Unless there's something close by, in which case to pause will be shorter.


You need to do a few things:


Test your motion code without the distance measuring code - but with the sensor mounted on the servo.  If it is smooth, then your servo has enough "muscle" for the job.  If it lags and jumps, then it is too weak.  You might slow down the motion and see if it gets smoother.  If you can't get smooth motion without the distance measuring code, then your servo is too weak.
Switch to a timer based library to control the servo.  This guy seems to have developed one for your board.  There may be better choices out there.  That's the first one I found.  This keeps a steady train of pulses going to the servo even when you are measuring distances.
Realize that each distance measurement will take some time, and it will vary depending on what your sensor can "see."  You will never get perfectly smooth motion since you have to measure distance in your motion loop.
See if there's a timer and interrupt based library for your sensor.  It won't improve the motion problem, but will deliver more reliable distance measurements than your software loop.