It is the same for the boolean modifier (and the same for text objects).
Only difference to the modifier is that the modifier actually filters these object types out and you cannot pick them as targets at all (this is where Geometry nodes are weaker -- they dont tell the user UI wise...)

D11272: Boolean targets can now be any object providing a MESH in GeometrySet is related, same thing could be done for (bevelled) curves.
T89457: Font remesh bug in modifier stack. is also related.

Pasting a conversation with @Hans Goudey (HooglyBoogly) from blender.chat here

Just checking if text objects as inputs for booleans in geometry nodes: are these supposed to work? [they dont in the regular modifier stack, in GN you can wire it up, but does not seem to work]

Currently it's "expected" that it doesn't work. Historically I think that's because curve type objects always evaluated to a "DispList" instead of a mesh. That is not true anymore, so it would be much simpler to make them work as boolean targets.
However, personally I'm a bit conflicted on that change, since the evaluation to a mesh is all implicit. Changing data types like that is something I think would make more sense as a node (which is sort of the idea with the curve to mesh node and a future 2D curve fill to mesh node).

So these nodes would more or less replicate what we now have for text/curve objects in the Geometry tab, right?

Yeah, that's basically the idea

@Hans Goudey (HooglyBoogly) : should we close this?