Yeah, we run into this issue on occasion, and the only good solution for us, unfortunately, is to turn off the blocking of field updates via flow change data values, make all the lead source updates we need to via smart list flow actions, and then turn the blocking back on. It'd be ideal if the options Steven mentions above could discern between triggered flow change data values and one-time batch changes.