I'll offer several observations with respect to my thoughts on prospective "enhancements". The basis for which is having been a long time registered TOAD for Oracle user and TOAD for MySQL, even back when it was not free!
1. I have to say the recent interface changes in TOAD for MySQL are well...wanting. It seems to be an attempt to make it into a pseudo-java style interface. The whole glare and gradient styling just makes it more difficult to navigate the tool bars and the icon sets are either too small or too big. I can only speak for myself, but I would rather have the various TOAD interface designs consistent across platforms and versions. Sure, progress and all, but I'd rather consistency. I don't much care if the tools I use are styled in the current fashionable way, I want them consistent. At least give me to choice to have it so. One of the reasons I won't use SQLDeveloper except under duress is the hideous interface.
2. One of the wonderful long time features of the TOAD for Oracle has been the popup data editor in the grid. When you have long text columns it makes viewing and editing data much easier and as a result, safer. Bring it back (I am pretty certain it used to be there in the "old days". I don't mean that weenie drop down, fly-out editor either, but the full featured one like it used to be.
3. Add the option for a confirmation popup dialog when changes have been made to data in the grid.
I know it is easier to be critical than have to implement, but these are things that used to be there. And keep in mind, sometimes "improvements" aren't.
I think you are confusing Toad for MySQL with Toad for Oracle. Unfortunately Toad for Oracle was written in a way where it was not feasible to add support for other database platforms using the same code base so when writing all the other "Toad for *" we had to start over from scratch.
All "Toad for (Insert database here)" except for Toad for Oracle are based on the same code base though and do have the same look and feel with minor tweaks here and there to accommodate differences that the database engines themselves might require.
In regards to point 2 you have something similar (I think) if you right click and do "Show card view" in the grid.
In regards to point 3 you have that option if you go into Tools|Options|Environment|Grid and change the option "Submitting changes to the database" to "Manually submit row changes as batch". Keep in mind that most table engines in MySQL does not have transactional support so once you post your changes to the table you have no way of doing a rollback on those changes.