The fix does not create load.
The hell it doesn't. Once I finally figured out that I needed to delete it a few seconds after it started running (or else it would spawn hundreds of more instances, as more users visit my site) - and even AFTER I added a sleep to that script, it still caused heavy load on my server for over an hour before I abandoned that method and just went in and edited the database manually. I think you fail to realize that servers effected by this issues have 1000s of these damn cron jobs to get rid of, and looping through them while the server is under load is just asking for trouble... especially if each visitor to the site causes another loop job to be spawned.
On top of that, this "Fix" was available on Wednesday, yet for some reason it has not been implemented in the 4.3 code which is currently available from WordPress. Which means 1000s more sites are being needlessly effected by this bug each day. I didn't install 4.3 on my site until Thursday, the day after this bug was fixed.