The key things wrong with Windows 11

Windows 10 vs 11
10: Lenovo - Intel Core i7-6700HQ (8 years old) [Version 22H2 Build 19045.6466]
11: Acer - AMD Ryzen 7 5700U with Radeon Graphics (1 year old) [Version 25H2 Build 26200.8655]

Open with focus
With Chrome open, click on any icon in Task Manager or Desktop.
10: that program opens and has the focus.
11: >50% of the time it opens behind Chrome.

Printing
10: Sends output to the printer every time.
11: About 10% of documents sent to the printer, requires running this .bat file

After running the batch file the document prints even before I log in. Then it prints just fine until the next time it quits.

Sleep
10: sleeps just fine requiring mouse or keyboard to turn on the screen and password to log in.
11: Sometimes it goes to sleep or not (so I turn off the monitor), sometimes it requires a password to log in and sometimes when I turn on the monitor I’m already logged in!

I suggest you start with a clean boot. If your issues do not happen in a clean boot, you have some software conflicting with Windows. You have to use process of elimination to find which one. While any app an cause such issues, look to any 3rd party app that alters the GUI being the problem. Perform a Clean Boot in Windows 11 to Troubleshoot Software Conflicts Tutorial

Make sure you have no corrupt system files that is causing this problem. Open a command prompt as administrator and type
dism /online /cleanup-image /restorehealth
When complete restart. Then open command prompt as admin again and run sfc /scannow
Pay attention to the scan results to see if SFC found anything it could not repair

Just to add to what glasskutter noted already, I think the steps given are a good idea because each of those issues seems to be an non-issue on many installations of Windows. For example, I run exclusively Windows 11 on all of my systems and not one of them has any of the symptoms that you describe.

Put another way, the problems you are not seeing don't happen on every machine so it seems likely that something that you have running or have configured may be the culprit.

To make your testing easier, consider doing an image backup before you begin so that you can easily return to where you are now, or better yet, consider installing a secondary installation of Windows for testing so that you don't mess with the current installation at all at least until you determine the source of the problem(s) are.