An attempt to run games and/or demos from floppy directly means, they see several things at once:
1. A 68040 CPU wich they eventually have no support for
2. A CPU with enabled caches (JIT cache) which will cause a lot of trouble if they are using self-modifying-code
3. An awfully fast CPU which they are eventually not ready for - e.g. the coder might have assumed that some CPU operations will be slow enough that a blitter which they use finishes operation before CPU - this may lead to catastrophic results (glitches) if coder does not wait for blitter ready before re-using it.
4. Eventually the game or demo is not even ready for more recent kickstart if they were jumping directly to ROM violating normal way of using the kickstart.
As someone else wrote - this is the reason why WHDLoad was created. It not only allows to use floppy-only games from HD, it also can adjust several critical things on the CPU before launching game/demo. Plus, as in case of Emu68, one can run EmuControl there in order to slow CPU down to a level which the game/demo is happy with.
One can adjust Emu68 parameters on boot already to solve at least some of this things but this is a tedious work, better use WHDLoad for that.