Mysql sync_binlog = 50 and innodb_flush_log_at_trx_commit = 2 with replication
Another way to get past these possible problems is to use a Galera Cluster (eg, MariaDB 10 or PXC).  With Galera, you can (should) be sloppy about such syncs; instead rely on the cluster's ability to recover automatically and efficiently from a dead machine, whether dead from power, OS, or whatever.  One caveat, though:  You need to make sure a single failure (such as power) won't kill all nodes in the cluster simultaneously.

With Galera, you can write and read any node.  3 is the minimal number of nodes to provide automatic recovery from the loss of any one node.  You can configure it to do all writes to a specific node, thereby pretending to have Master+Slaves configuration.  (In some applications, this is actually beneficial.)

Back to your situation.  Set both of those settings to 1 or the Master; set them to 50 and 2 for the Slaves, then...  If a Slave dies, assume it is corrupt and rebuild it; do not try to recover the data, since the necessary syncs may not have been done.  To lighten the load on the Master, don't send standalone reads to it.