The answers to your questions depend on the companies/projects. But one thing worked well repeatedly, is to show, real evidence to other team members "I can do real test automation" from Day 1.

Check out this article, "How do I Start Test Automation on Day 1 of Onboarding a Software Project?" https://zhiminzhan.medium.com/how-do-i-start-test-automation-on-day-1-of-onboarding-a-software-project-3b4596bb373

The reality is that, 99.9% of time, PM, developers, BAs and manual testers, never witnessed a single successful E2E test automation. They only saw failures (again and again). So, they won't believe this new test automation engineer, thought, "it was just like Jira or another so-called ceremony to make it appear Agile".

Back to your questions.

Secnario 1:

When the developers trust me, they would listen to add IDs. Often, I wrote good Xpath though.

Secnario 2:

Before the team trusted you and see the great benefits of your E2E test automation (usually I took me a few hours), my advice is "better keep mouth shut", for the reasons earlier.

So, keep learning and be efficient and productive on E2E Test automation. Practice and Practice in spare time. Let your E2E test automation script and execution speak!