The conflict simulation page was originally build to allow easy testing of the beta interface, especially to allow user tests during the beta phase and when implementing the newer UI. The simulation page has some drawbacks though.
- the simulated conflicts are mostly not "real" conflicts due to the randomness of how this behaves
- the simulated conflict does not allow a preview
- the way the conflicts are simulated is quite tightly bound to how the EditPage is implemented and would sooner or later need a refactoring
When external users as main target group for the simulation page become irrelevant it might be better to get rid of the simulation page code so it does not burden us in the future. If we internally want to quickly create conflicts there are other easy ways to do that using custom scripts that automate this process. e.g. @awight created one of these