Generally, I am strongly against influencing migrations to new iterations of the protocol by using Reserve Factor increases.
If there is no big need and no other mechanism available (e.g. FEI), I don’t believe it should be within the ethos of the community to use the RF knowing that the protocol itself will profit from it. For ethical reasons even.
Modifying coverage by the Safety Module is also a sensitive topic, even if I think worth it to consider. If as a user you start using Aave considering it as a unique selling proposition the potential coverage by SM, open a collateral & borrow position, and then the governance decides to just remove it, doesn’t give too much stability.
That being said, the dynamism of the Aave community continuously coming up with improvements and updates should be taken into account, so given that removing the SM coverage from v2 doesn’t really profit anyhow the Aave system, I think it could be acceptable, at least somehow progressively.
Regarding listings, I think it is pretty clear at the moment for the community that doesn’t really make any sense to have listings of v2 versions unless something exceptional. So I would probably signal with a proposal that, apart from if there are assets already in the middle of the process, no more listings on v2s.