This happens also on version 12
The reason for the error message
sys_redirect table is not allowed on standard pages
How to proceed
I think this depends on the answer to the question: "Should redirects be allowed on standard pages?".
If yes
It might be simple: "[BUGFIX] Allow sys_redirect on standard pages". (I could provide a patch, if needed)
If no
In this case we assume that sys_redirect is not allowed on standard pages for good reasons. For example: Avoid spreading redirects in page-tree, ...
The auto-redirects, however, get stored on standard-pages (the page which has a changed slug), which, on copy-pasting a page, leads to the attempt of data-handler to insert redirects on a target which is a standard-page. Summary: auto-redirects are created on standard-pages although not allowed by TCA.
Therefore, i see two more interesting possibilities to tackle this:
1) Change redirects extension to not create redirects on standard-pages (might be quite some work)
2) Introduce an option to exclude tables to be copied along with pages (would not directly address the issue and is rather a feature than a bugfix)
The reason I think 2) can be an option is that copying redirects along with pages could be wrong in many many cases. I'd think redirects belong to the copied pages most of the time ... unless it's a copied sys-folder, were the redirects are some kind of "pack-of-disabled-redirect-templates" or so. However in that case, it would still be possible to reactivate via TCA and allow sys-redirect entries on standard pages, on project level.
I provided a WIP patch for 2, in case it is considered a good solution.