The SSD manufacturer previously known as Fusion solved part of the problem. The "doublewrite" buffer in InnoDB prevents corruption that can (very rarely) be caused by "torn pages". Since InnoDB likes to write 16KB at a time, but devices like to work in smaller units, a 16KB page could be partially written during a power failure. The doublewrite solves that by writing the block twice. Fusion IO, instead, guarantees atomic writes for the 16KB pages.
Another manufacturer, Violin, streamlined the data path so that a cache is not needed. It does not return an ACK until the write is completed.Is this what you are looking for?
A RAID controller with Battery-Backed Write Cache also solves the problem for both HDD and SSD. Even with HDD, writes can seem "instantaneous".
Virident (now part of HGST) had a capacitor big enough to allow flushing its cache.
With Galera, you can turn off all the IO protections. Instead, rely on Galera's ability to recover a crashed node at a higher level. (This assumes you don't have all the nodes co-located.)
Back to your proposal. First, this forum is not the right place to propose it. Instead, I recommend you write out a few more details and file a feature request with
http://bugs.mysql.com . That is the 'right' place to provide suggestions (as well as bugs and documentation changes).