Yes, contrary to what I first said, this is not a case that would get optimized.

This proposal only prevents re-virtualization in call chains, which
means you are free to write:
devirtualized.a().b().c()

instead of:
devirtualized.a()
devirtualized.b()
devirtualized.c()