The program I am debugging spams c0000005 exceptions basically constantly during normal behavior. It has an access violation hook registered, and uses access violations as a mechanism for delayed memory mapping of hosted code and plugins.

When an exception happens, remedybg seems to steal focus back from the program, meaning I cannot interact with it.

Is there a setting to work around this, or is this something that could be considered a bug in remedybg?

One thing you can try is to disable breaking for an access violation altogether by opening the "Event Filter" window and unchecking "Access Violation (0xC0000005)". Then, the process won't be suspended at all.

There is a way to control behavior of this via the driver API (RDBG_COMMAND_SET_BRING_TO_FOREGROUND_ON_SUSPENDED) but that's really not straightforward to have to deal with in this context.

If the first suggestion isn't sufficient we can look at adding an option to toggle this in the UI, instead.