https://html.spec.whatwg.org/#dependencies (scroll to SVG, there are no IDs to target those dt)

It has a bunch of text about wilful violations, implementation status, and a list of things not to support from SVG 1.1 and things to support from SVG 1.2 Tiny.

Should this just reference SVG2 now?

Things it says to not implement from 1.1:

• The tref element (removed in SVG2)
• The cursor element (use CSS's cursor property instead) (Will probably get removed. Safari still supports)
• The font-defining SVG elements: font, glyph, missing-glyph, hkern, vkern, font-face, font-face-src, font-face-uri, font-face-format, and font-face-name (use CSS's @font-face instead) (Removed in SVG2)
• The externalResourcesRequired attribute (Removed in SVG2)
• The enable-background property (Removed in SVG2)
• The contentScriptType and contentStyleType attributes (use the type attribute on the SVG script and style elements instead) (Removed in SVG2)

The things from the dead SVG 1.2 Tiny spec are implemented by browsers and included in SVG 2 (or in the mixin in HTML for tabIndex)

Should it be updated to something like the following?

SVG
While support for SVG as a whole is not required by this specification (though it is encouraged, at least for Web browsers), certain features depend upon parts of SVG being implemented.

User agents that implement SVG must implement the SVG 2 specification.

The following features are defined in the SVG specification:

• SVGElement interface
• SVGImageElement interface
• SVGScriptElement interface
• SVGSVGElement interface
• SVG desc element
• SVG foreignObject element
• SVG image element
• SVG script element
• SVG svg element
• SVG title element
• SVG use element
  (perhaps include the features that were listed from 1.2 Tiny here?)