hv-tlbflush-direct can be useful to optimize performance in nested virtualization cases, such as Windows VBS.
hv-tlbflush-extended can also help and is not limited to nested scenarios.

At least up to 4.19.10

We can control tlbflush, but not tlbflush-direct/extended

# oc explain vm.spec.template.spec.domain.features.hyperv | grep Object
FIELD: hyperv <Object>
  evmcs	<Object>
  frequencies	<Object>
  ipi	<Object>
  reenlightenment	<Object>
  relaxed	<Object>
  reset	<Object>
  runtime	<Object>
  spinlocks	<Object>
  synic	<Object>
  synictimer	<Object>
  tlbflush	<Object>
  vapic	<Object>
  vendorid	<Object>
  vpindex	<Object>