Can't you try your copperlists on WinUAE, or other UAE variant?
Which issue are you a talking about ....
There are 2 or even 3 different.
1) Issue w/ WAIT instruction for horizontal position $E2.
It is confirmed on a minimig HW. If you wait for horizontal position $E2 Copper will not 'cautch' beam match for it. When WAIT position is changed to $E0 it behaves correctly
2) Restart Copper by COPJMP write if it is stopped by illegal address.
Copper list from point 1 uses MOVE instruction to restart copper. In a simulation (hpos wait set to $E0) waveforms is correct and behavior is the same as on a real minimig. It means that simulation of MOVE $0080, $0000 it is correct.
When you look at a simulation result, when copper is stopped, write to COPJMP register seems to be discarded. Simulation of my copper code gives the same results as simulation of original verilig code. I have even use it to build a bin file. Dexion "Megademo" works great w/ it. I've started "F..ing copper" part at the same time on winUAE and minimig and there was no differences in behavior and timing.
The only simulation difference (between minimig and my design) is that in my code Copper is restarted (from a stop state) when COPJMP write is issued by CPU. Minimig seems to stay in that state until SOF apprears.
3) Behavior of Copper in case of CDANG set when it was stopped by write to restricted range (for detailed description see post above).
I couldn't find any information how it shall behave. That way it is mentioned as a possible issue