IIRC, I did hear something similar a while ago, that iOS puts UI updates on the highest priority (basically system interrupt?) whereas android does not. IMO it's the right way to do things - no one should tolerate an unresponsive touch UI any more than they should tolerate a mouse cursor that wasn't responsive.
Regardless, is there any way to modify this behavior?
This is not correct, it is much more complicated.
First it is java garbage collection that is the biggest remaining issue now.
Then there is not really a dedicated UI thread that alone is enough to render the updated frame, you often need updated data from the main thread.
And give a UI thread high priority is in general bad from stability point of view. It means that you could stall crucial tasks justs by bonking on the user interface.
Render a cursor is a quick and well defined operation, not comparable to an unknown UI operation.
It is not really Android that is bad but rather ios that is extremely fine tuned from the beginning to be lag free with slow hw (e g iphone 1).
But with ART that will be default on in L, the lag from garbage collection will be greatly reduced. And many other improvements have been made in 4.x.
And Android have always been a more open framework with more apps using background tasks, sometimes these background tasks collide with main task causing lag.
Especially the storage system (simple eMMC controllers) tend to lag when you write to several files at the same time. This will also improve with better eMMC controllers (e g eMMC 5.0).