Automate detection of socket.checksum when node joins the cluster

Its a feature request.

When a Galera-3 node joins an existing cluster consisting of Galera-2 nodes, it fails to join with the following error unless socket.checksum is set to 1 (default in Galera-2).

Feb 17 11:51:26 mysql05 mysqld: 140217 11:51:26 [Note] WSREP: view((empty))
Feb 17 11:51:26 mysql05 mysqld: 140217 11:51:26 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out)
Feb 17 11:51:26 mysql05 mysqld: #011 at gcomm/src/pc.cpp:connect():141
Feb 17 11:51:26 mysql05 mysqld: 140217 11:51:26 [ERROR] WSREP: gcs/src/gcs_core.c:gcs_core_open():196: Failed to open backend connection: -110 (Connection timed out)
Feb 17 11:51:26 mysql05 mysqld: 140217 11:51:26 [ERROR] WSREP: gcs/src/gcs.c:gcs_open():1291: Failed to open channel 'cluster' at 'gcomm://192.168.5.98': -110 (Connection timed out)
Feb 17 11:51:26 mysql05 mysqld: 140217 11:51:26 [ERROR] WSREP: gcs connect failed: Connection timed out
Feb 17 11:51:26 mysql05 mysqld: 140217 11:51:26 [ERROR] WSREP: wsrep::connect() failed: 7
Feb 17 11:51:26 mysql05 mysqld: 140217 11:51:26 [ERROR] Aborting

Now, since the default socket.checksum is 2, it is more likely to happen.
https://mariadb.atlassian.net/browse/MDEV-5691

Is there a possibility where the joining node can detect this and auto-adjust its socket.checksum value?
Can same be done for other version incompatible changes (if any) too?