There are a number of reasons you might want to avoid this. Some are reasonable, some are not.
The first is disk space: this is the most basic. If an app depends on just Qt, that's not too bad (although Qt is still rather large). If an app depends on part of KDE, however, you are likely to essentially pull in all of the KDE library stack, which will probably total several gigabytes of storage (I'm not sure as I've never done this due to the reasons I'm listing now). This is because the layers that make up desktop environment stacks tend to be interdependent, and the higher levels of the stack will pull in the lower levels. Programmers are unlikely to use just the lower levels of the stack.
The second reason is integration. If you're running something from the GNOME family, like GNOME Shell, Cinammon, or MATE, a KDE app isn't likely to integrate well into your environment. This is because the app expects the KDE version of things like notifications or the system tray to be there, instead of the GNOME version, and can't deal with the difference. Therefore, you may experience ugly UIs or the fact that certain niceties are gone.
The final reason is the most religious and unreasonable: purity. Some people feel that if you have GNOME and KDE libraries simultaneously installed, you have destroyed the "purity" of your GNOME system and the OS has now been "dirtied" with the KDE libraries. This feeling has no technical basis, but a lot of people do feel like that (including me, I must admit) and will therefore avoid pulling KDE libraries in as dependencies (or, conversely, avoid pulling in GNOME libraries into their KDE systems).