There certainly is a way, but it would be an awkward solution, and it is conceptionally wrong, too. If the IDE's burns too many CPU cycles (not an apparent problem here, though), then the number of cycles spent must be reduced, not its priority adjusted.
Fiddling with priorities is generally not a good idea unless there is a good reason, as it hurts performance more often than it helps. The same is true for things like locking memory pages, purging free pages, and setting CPU affinity masks. In most cases, such "optimizations" make things worse, not better.
Nevertheless, a lot of people do it, and "memory optimizer" tools are still being sold for real money, which is beyond my comprehension...
