V3 transaction policy for anti-pinning

How crazy would it be to implement a variety of options for the descendant size? For example:

  • v3 == 200 vB (value suggested by Peter Todd)
  • v4 == 400 vB
  • v5 == 600 vB
  • v10 == 1600 vB (max LN historical size observed by @sdaftuar)

Then each use case could decide for themselves.