Agree with outcome of investigation, and just some additional comments:

Re state, suggested approach by redux would be to test redux functionality itself ala unit tests for redux where we test that the redux bits like the actions and reducers are doing what they're supposed to be. This could mean some overlap if we're testing component state in our component unit tests. Some small research might be required to see where to best draw the line between state-testing in redux and our component unit tests.

Re E2E testing frameworks, if E2E testing frameworks come into the scope of this investigation, it may be worthwhile to consider Cypress.