Overriding player movement in PlayerMoveEvent causes a PlayerTeleportEvent

Expected behavior

If I override player movement in a PlayerMoveEvent, it should not call a PlayerTeleportEvent. I believe this is a genuine oversight, while it is niche I do believe it needs to be addressed for consistency

@EventHandler
public void onPlayerMove(PlayerMoveEvent event) {
        // Why does this call PlayerTeleportEvent ?
        Location to = event.getFrom();
        to.setPitch(event.getTo().getPitch());
        to.setYaw(event.getTo().getYaw());
        event.setTo(to);
}

Observed/Actual behavior

When using the above logic to override the player movement, it calls PlayerTeleportEvent,

Steps/models to reproduce

public class Main extends JavaPlugin implements Listener {
    private static boolean shouldFreeze = false;

    @Override
    public void onEnable() {
        getServer().getPluginManager().registerEvents(this, this);

        getServer().getScheduler().runTaskTimerAsynchronously(this, () -> {
            shouldFreeze = !shouldFreeze;
        }, 20, 100);
    }

    @EventHandler(priority = EventPriority.MONITOR)
    public void onPlayerTeleport(PlayerTeleportEvent event) {
        getServer().broadcastMessage(event.getCause().toString());
    }

    @EventHandler
    public void onPlayerMove(PlayerMoveEvent event) {
        if(shouldFreeze) {
            // Why does this call a teleport event?
            Location to = event.getFrom();
            to.setPitch(event.getTo().getPitch());
            to.setYaw(event.getTo().getYaw());
            event.setTo(to);
        }
    }

}

Plugin and Datapack List

N/A

Paper version

[01:23:50 INFO]: This server is running Paper version git-Paper-61 (MC: 1.19) (Implementing API version 1.19-R0.1-SNAPSHOT) (Git: cd215af)
You are running the latest version

Other

No response

Start by reproducing the supplied listener with PlayerMoveEvent and PlayerTeleportEvent on the reported Paper 1.19 version. Trace how changing PlayerMoveEvent#setTo produces the teleport event, then verify that movement overrides no longer emit PlayerTeleportEvent while genuine teleports still do.