In the emulator plugin version 2.13, the emulator startup check was changed from dev.bootcomplete to init.svc.bootanim (reported in Issue 11952). This seems to be the right way to do it. However, because of the -no-boot-anim flag in the emulator, this does not work at all. The device will be reported as being ready way too early, and a long time before the dev.bootcomplete property will have value 1. This is also the reason that the emulator seems to be starting much faster in the most recent version of the plugin.
One solution would be to remove the -no-boot-anim flag. However, this will increase boot-times a bit which is probably unnecessary for some users. Another solution is to make a setting to control how the emulator will be started.