If you\'re connecting the digispark over USB and interfacing it with a program, you can ask the bootloader to run the program immediately just that one time, so then the delay is just however long the operating system takes to enumerate the device. Roughly half a second. If you\'re writing a program in C you can use micronucleus lib to control the bootloader, including causing it to run the program:
https://github.com/Bluebie/micronucleus-t85/tree/master/commandline - there\'s also some code written in ruby to do the same thing.
There is some opportunity to experiment with detecting the USB SOF pulses, so the bootloader could exit after 100ms or so when powered on if it isn\'t connected to a computer\'s usb port which isn\'t asleep - i.e. usb chargers or power connected via the pins on the digispark. I haven\'t tested this theory so maybe it wouldn\'t work.
It\'s also possible to remove the bootloader if you\'re sure you wont want to reprogram the digispark or have access to a high voltage serial programmer to restore the bootloader later when needed. All it would take is rewriting the first 6 bytes of flash memory. It takes a bit of care, but it\'s not too difficult. If you don\'t need the first four interrupts you can just write it all to 0\'s and then it\'s downright trivial.