This is certainly not a Remote Buddy App Nap issue. That issue was isolated, reproduced, fixed in 1.24.2 and subsequently also verified with Apple. All affected users who got in touch also let me know that release fixed it for them.

Other applications, though - unless they adopt the new App Nap API - can theoretically still be put to sleep by Mavericks. They could then suffer the same responsiveness issues as any other app.

What could be happening here is that XBMC gets put to sleep by OS X. I don’t think that the UDP packets sent by Remote Buddy to XBMC would make OS X wake up XBMC, though giving XBMC keyboard focus and entering something on the keyboard most definitely will.

To find out whether XBMC is suffering an App Nap issue, open Activity Monitor.app, switch to the „Energy“ pane and watch the „App Nap“ column for the entries of XBMC and all of its helper processes. If XBMC stops responding and you see a „Yes“ there, App Nap has put XBMC to sleep.

Your Remote Control Diagnostics output is also very interesting and identifies a lot of possible issues. Though, for me to see the complete picture, please select „All“ on top of the window and copy and paste the full output in reply.

Thanks in advance.

Best regards, 
Felix Schwarz