MG,
if I understand your point right, you are complaining about two things:
That for any graphics X is needed, and that X is a large beast. Well, that's partially right, but also depends on the point of view.
First thing is settled?: You either need some graphics capable console, which requires some kernel module ("driver") which makes GPU's graphics capabilties to be available. Or otherwise you have a text only console. Which also can be set to a higher resolution (add
efi_max_resolution="1920x1080" to your
/boot/loader.conf [see handbook or search the forums for details, it's all several times in here]) and maybe pick another font.
vidcontrol(1) is the tool #1 to provide easy configuration on that. But no graphics, but ASCII art. So, just to be clear: You are either in text only mode, or you have some kind of graphics console.
For a graphics console there are two common ways: good, old classic X or Wayland, because for some X was too old, too bloated, too complex, too ... anything, so they started a new thing. However, both have their pros and cons, and there may be others, but I simply don't know any else than those two providing a graphics console for unix[like] or Linux.
If you complain X was too large, too bloated, too complex, especially for primitive jobs, you may be right. But that leads to the common discussion about software at all: If you want something autoinstalling, so respecting almost every kind of hardware - graphic cards are one of, if not
the most complex troublemakers in computers of the last fourty years; and each is very different; while it all shall work automatically turnkey, without the user's need to care about it much, and want to have 2D AND 3D graphics support, and this, and that, and this must also be in, and that's indispensable... - of course the beast eventually become bloated. It's the same thing with FreeBSD or some turn-key single user desktop Linux distro: you either get some large (bloated) beast, autoinstalling lots of crap you neither want nor need but you don't need to care about in detail, or you get a very basic system and need to install additionally by yourself all and only the things you need and want. Which needs learning, what there is, what to pick, and how to do the installation and configuration. But you simply cannot have both. Impossible.
And X came a long, long way, baby. Many here still remember the times, when we had to deal with mod lines, flickering or distorted screens, being worried about the monitor's tube blow up... In those days the 300M you mention (I actually don't know how large my X on my machine is, because I don't really care, but that will be this next point exactly) were a number, a large number you recognized in downloading times, and storage space. But what are 300 M today? What are 0.3 G on modern storage device, especially as a system's drive? I often recommend a 64 G ... 128 G was enough for FreeBSD. Apart from you need to pay extra for such a small drive, I hera people read this laughing, because who today runs a machine with less than some 512 G drive? Nobody. So, you just live with it, and don't care. For sure it's some kind of waste. But so it is to store a '1' in some 64bit memory place.
Except - and that will be my last point:
On some kind of an embedded system, some ARM, Rock, RasbPi,... something like that, if you really need to save space, or want to not have some features onboard, for whatever reasons.
Well, then apart from accepting the given there is two other ways:
Compile X (or Wayland) with your personal modifications, so to get your own stripped down version of X (but don't expect, any of your DE, Office, browser, and what else you have then will run out of the box), or - since to me there are no other alternatives but X and Wayland are known - program your own graphics console.