If same can be achieved without bridgig, then this option may be preferred. Bridging is appropriate for P-V conversion and during the time that Physical and Virtual machines exist on the same IP subnet, but after the VMs are migrated to VXLAN and no other physical machines remain for this subnet bridging for this Vlan-Vxlan pair may be turned off. One use case may be if there is a site without NSX, and this site has some VMs (as hyperv, kvm  or cloud)  there a need to keep these  VMs on Vlan side, and using other L2 extension technologies for making these segments connected. Even for this scenario L2VPN edge can be installed as a standalone edge to provide this connectivity. If vSphere, I can't think of neccessity of keepeing the  some VMs for certain subnet on Vlan side, and some others on Vxlan side other than during migration.

If the default gateway is Physical L3 switch, for the Vxlan VMs as well as Vlan VMs and Physical Machines, the benefit of using Distributed Routing to increase throughpu is lost t,  as it decrease delay between VMs  and load on the Physical L3 switch.

Load Balancing to Vlan and vxlan VMs might be possible, but again best practice may be to keep VMs on Vxlan side

Regards,