I understand your rationale, and like me I would like to use 64-bit products where ever possible. However.... :)
Recently, in the process of migrating MDBs to MySQL for many of our customers we ran into the following problem.
Workbench (WB) 6.3.9 and 6.3.10 don't support 32-bit ODBC connections in the Migration Wizard, as WB is only released in 64-bit flavour. A 32-bit ODBC connection type is important when migrating from 32-bit MS Office environments (ie MDBs/ACCDBs) and as, AFAIK, you cannot connect 64-bit ODBCs to a 32-bit MS Office environment.
So we are in a bit of a dilemma here. I tried the Migration Wizard in WB 6.3.8 32-bit, however I ran into bug https://bugs.mysql.com/bug.php?id=83616
So I went back to WB 6.2.5, which doesn't have this bug. Yes, the Migration Wizard works but this version (ie 6.2.5) doesn't support the latest set of tools and server (6.3.x) and produces errors. Far from ideal anyway, as you want to go forward, no backward.
2 options IMHO:
1) Again provide future releases of WB in 32-bit, to allow for 32-bit ODBC based migrations, or;
2) Have future 64-bit WB releases support both 32-bit and 64-bit ODBC connections.