@Anonymous
I could not agree more. Making copies of drawings and xrefs, and switching the xref paths to the copies so you can rip and tear (well, erase and detach), is indeed tedious.
Luckily though, its simple. The trick is to keep a copy of the copy, so when you erase the stuff that causes the problem, you can go back a step and see what was there. More good news I know - copy of the copy...
Pretty soon, your whole day is used up, you isolated the issue, and........its an autocad bug you can't do anything about.
Story of my life, and its not fun when there are 40 xrefs involved.
Understand that it absolutely could be hardware related. My laptop sometimes does not have the jerky cursor when a user of mine is getting it. But we don't have spare different vid cards laying around to beg our IT group to test out for us. In the end, we either isolate the problem(s) in the drawings and do something to fix, or we switch to bricscad for the drawing with bad behavior. I know @RobDraw has not embraced bricscad yet, but I encourage all cad operators to get a seat of it so they have plan B at least. You might still pay for acad, and should if you make dynamic blocks and deal with point clouds, but Bcad is a one time $800 purchase, compared to $1500 a year for acad. If you like bcad, drop acad for a year and you save a ton. I'm pushing forum etiquette by saying this, but if the adesk team cannot solve this cursor bug, I get some leeway.
Now for something really nerdy, my company chili contest entry theme was "Bricscad is the new Autocad" but in chili disguise. The joke is always that a team will just buy canned chili and enter it as their own. So I wrapped cans of the same chili with these labels you could see through a bit, to imply you won't know the difference. Its getting complicated, here is the pic of the cans:

internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties