It would be great indeed.
There is an enhancement JIRA (DERBY-3927) that requests similar type of functionality. Please feel free to add to it.
Our site has gone live with Derby replication, and we are now setting up monitoring of the various services. Our sysadmin has asked me if there is any way of monitoring the health of derby replication, similar to MySQL's 'show slave status'. Currently we are scanning derby.log for suspicious-looking messages, but that's not ideal.