This is like a recommendation to stay on 7.23 until the problematic printer goes out of service. And when security problems require to upgrade at some point - you still bite the bullet. Better solve the issue now than postpone to "someday".
I'm looking at new printers 12 months on from my last problem where I had to buy a new Ipad because my perfectly good old one did not want to play with the settings I wanted to use. The reason I use Mikrotik is like everybody else, I want the best I can get for my money. And yes I want all the new features that go along with that. Why wouldn't I. It just puts me off wanting to add the New Be3 to my collection to add smart locks and door cam which I feel is the right move with said equipment and be safe when I use that stuff. So yes I need to keep moving forward and by proxy spend more cash on other unexpected items.
You should apply the same logic (proceed with security fixes) to those gadgets as well. According to this logic, also producers of doorbell buttons, printers and dishwashers should regularly apply fixes to their networking stack ... to remain compatible with whatever state-of-art of APs is. Do they? If they did, their gadgets at least would ignore AP features they don't know about instead of panicking and disconnecting.
If you wander into some rural godforsaken land, where they still use horse-pulled carts on their dirt roads, with your shiny new Maserati mcpura ... do you expect them to widen and pave their roads for you? Or do you rather go there with 3 generations old Toyota landcruiser (3 generations old because you want to be able to fix it using sledge hammer instead of computer with OBD interface).
Or, to reverse the perspective, if you wander into some rural godforsaken land where there are no paved roads nor cars and you have to improve their mobility, do you build a modern 6-lane motorway ... or a sturdy gravel road (mind that horses don't do well on asphalt-paved roads, they prefer something less sturdy, gravel roads are just perfect for them).
All your arguments are just badly made, obviously you build datacenters especially in rural places where land is cheap
Based on this...
It's better to rent a printer for work (I wrote for work).
It seems like you pay more, but you save time.
Even if my phone connects to Wi-Fi but the printer doesn't...
you can expect to get a new printer to replace the obsolete one for free...
And here, though... there's no way I'd use a Wi-Fi printer for work... But that's another story.
Care to elaborate?
Point of my discussion was that one can not realistically expect that modernizing one part of a system will not alter the way it works if the rest of the system doesn't follow (and in case of wireless devices, system consists of both AP and stations). Yes, idealistically that should work because things are supposed to be backward compatible ... but in reality some things are not compatible enough (e.g. stations which don't gracefully ignore unknown AP features).
Another example: many of modern 10Gbps RJ-45 NICs don't support rates lower than 1Gbps. Should I complain to NIC manufacturer because it doesn't link with my old 100Mbps ethernet hub? Yes, I can ... but will it help? Probably not ... and I'd be better off modernizing the switch side of my network as well. Or purchase lower-spec NIC which does support lower speeds (but doesn't support multi-gig speeds).
Yes actually i do care to elaborate.
The arguments made are plain stupid and printers are genuinely badly made, especially the wifi aspect itself on them. You can stick an AP inside it and it would never work well, whether that ap is wifi 1,2,3,4,5,6,7 or 8 it doesn't matter, the WPA protocol does matter, and what's not compatible with WPA 3 should be compatible with WPA2, well yes. but actually no.
Printers are made by satan to make living on this planet hell, you cant convince me otherwise, no amount of added tech to an access point can alter the backwards compatibility with devices by adding new features, the devices connecting should simply be "hey i can use this and that and that just give me that the rest doesn't have to be broadcasted for me. (and i might be wrong but some stuff already does that for example wifi 6 some stuff doesn't support mu-mimo or ofdma or twwt that's supported on wifi6 and it connects without issues, guess f... what, printers don't care.)".
That's exactly why u don't buy cheap printers that don't have eth ports, wifi is not the future.
Even tho your network is 100% configured to be backwards compatible with old devices/IoT, whatever, printers sometimes just don't care and you can give them everything in this world to make them work, its just not gonna work (sometimes its an OS issue, win11/10, sometimes its a bad driver issue, sometimes its a network configuration issue, sometimes its all of the above, i really wish and hope you get to experience printer hell at least once in ur life, it builds character faster than anything).
Can give only one, but really:
Damn, we're going ot, I didn't realize this is the 7.24.1 topic....
I somehow assumed that your response was to my post directly above. Your elaborated text makes me think that we actually agree on this.
So we are back to it's my printers fault 
I incline to agree that often it is actually a problem with "appliance" and not the network. Many cheap printers which have only USB and WiFi connectivity have problems with compliance what comes to WiFi. It can be some sort of non-standard-compliant "power saving" algorithms which cause all these disconnects. With some devices it can be solved by tweaking networking settings, with others it can be just a waste of time i.e. cost/value of this printer is less than labour costs for futile troubleshooting.
I remember how we had one Brother printer which was flooding logs with these endless disconnects no matter what to do. Strangest part of all this was that users did not complain because even with this patchy connectivity all print jobs did succeed and users just did not know there was a problem flooding connection logs.
To anybody who has to manage printers, especially inkjet ones, especially wireless ones: you have my deepest admiration.
Otherwise 7.24.1 installed on the test tower and might promote to prod next week. Who knows.
Do people actually buy printers without an ethernet jack?
Never eth cable for printer ! It's easier to throw them out the window when things go haywire.
When standard interfaces were a thing, I tended to drive my printers direct off a server, and not the network, although now with the flakiness of USB and it's disaster area of proprietary drivers, I do it less and less . . . . I have one that is just USB or WiFi that I bought in despiration, but the WiFi seems to work OK. (I still spool through my server though . . . )
I do miss serial/parallel, and a standard PostScript interface . . . .(I guess it was just too easy!) 
I don't know how things are standing now, but when I last went out to purchase a printer for my home, I had three hard requirements:
- it has to support PostScript so that I don't need some buggy vendor-provided driver for my Linux machines
- it has to support ethernet jack so that I don't need some kind of "printer server" gadget to use it from all the devices in my home (so serial/parallel/USB port didn't matter, WiFi didn't matter)
- it must not be prone to "ink solidification" problems due to infrequent usage (which rules out all the inkjets)
And there actually were quite a few models ... at home-friendly prices as well (got some Brother laser at around 200€, replacement toners come at around 50€ for set of 4 toners). It does have USB port and WiFi ... and I actually do use USB port to connect to my better half's company laptop because that laptop has VPN enabled at all times (out of company network) and can't connect to home LAN devices which includes printer (and company's IT guys agreed to install correct printer driver but not to enable LAN access).
That's close to where I am . . . . HP Laserjet Pro 400dn . . . . USB, Network, Postscript and PCL. I still choose to spool it via CUPS from my Linux server, but feed it PostScript via the network. (CUPS gives me support for just about any platform, along with full feature support.)
More of a mid tier commercial printer, though, so I did pay more than home pricing.
Not necessarily needed for this one, but I find HPLIP to be very good at supporting even the goofball proprietary HP printers while others (like Canon) can't even spell "Linux" much less support it.
This topic apparently turned to "printer buyers guide". 
My favorite home printer is the Epson Ecotank 4850 via ethernet while all my wireless devices access it flawlessly via airprint ... very economical to operate and excellent built-in maintenance tools ...
My favorite printer is the one that always works when I like/need to print something. Still searching....