The problem: You now have double the test code
With Protractor going EOL, every new line of Protractor test code must be written twice; once today, and again in the near future for a modern and well supported test framework.
Projects are further hampered by the inability for Protractor and modern testing frameworks to exist in parallel, as namespaces and tooling collide. This means migration away requires dumping your tests or paying to rewrite them.
If only you could maintain your existing test suites while investing in new tests on modern technology...