Yes, this is automatically fixed by 4.3.1. Both the issue with the reversed parameters and the extraneous cron entries are fixed.
If you still have the issue, updating to 4.3.1 and performing any "database update" it asks of you will solve it immediately. The auto-upgrade process or the one-click upgrade process will perform the database fix automatically; there are no extra steps required there.
For multisite installs, you must perform the "Upgrade Network" step for it to run the database fix over all the sites in your network.
If you still have the mu-plugin I originally posted about on page 1 of this thread, then you can remove it. It is not necessary with 4.3.1.