G: TL;DR: On a Raspberry Pi 4B, running Windows apps via Wine + box86/box64 feels roughly like a late-1990s/early-2000s PC—think a fast Pentium II to early Pentium III (≈400–800 MHz) class machine for most 2D apps and older games. A Pi 5 bumps that to roughly a late Pentium 4 / very early Core Duo vibe for CPU-bound stuff, still well short of modern PCs.

Why that’s the ballpark

Wine on ARM isn’t native x86: you’ll use a translator (box86/box64 or FEX) which typically costs 2–4× performance versus native ARM code.
Pi 4B (Cortex-A72 @1.5 GHz) → after translation overhead, integer performance lands near that Pentium II/III era for typical Win9x/Win2000 software.
Graphics: Old DirectDraw/Direct3D 7–8 titles and 2D apps are fine; heavier 3D or anything shader-hungry is the bottleneck. Expect 1998–2003 era games to be the sweet spot.
I/O & RAM are better than period PCs, so loading and multitasking can feel snappier even if pure CPU isn’t.

Practical expectations on a Pi 4B

Comfortable: Office 97/2003, Winamp, Notepad++, lightweight utilities, StarCraft, Diablo II, Age of Empires II, Half-Life 1.
Borderline/finicky: Morrowind (tuned), later DirectX 9 titles, anything that really wants SSE2 or strong GPU features.
Generally no: Modern 3D games, heavy multimedia editors, .NET/WPF-heavy apps.

If you’re on a Pi 5

Use box64 or FEX + Wine. You’ll get a noticeable jump—still “old PC” territory, but closer to late P4/early Core era for older apps, and a few more DX9 things become tolerable.

How to squeeze more out of it (quick hits)

Prefer 32-bit Wine when possible (lower overhead).
Use OpenGL renderers or wrappers (dgVoodoo2, DXVK for very old DX9 if it helps).
Overclock conservatively with good cooling.
Stick to portable/older app versions that don’t need modern drivers or .NET.

If you tell me your exact Pi model and what apps/games you care about, I can map them to “likely fine / maybe / probably not” tiers.

G: On your Lenovo ThinkPad X1 Carbon 6th Gen, you’re in a very different league compared to the Pi.

Hardware baseline

CPU: Intel Core i5/i7 8th gen (U-series, ~1.6–1.9 GHz base, turbo 3.6–4.2 GHz).
Cores/threads: 4C/8T.
RAM: Usually 8–16 GB DDR3/LPDDR3.
GPU: Integrated Intel UHD 620.

Running Wine on Fedora

Wine doesn’t emulate the CPU—it translates Windows API calls into Linux equivalents. That means apps run at near-native speed, limited mainly by driver translation layers.
Overhead is typically 5–15% compared to running the same software natively on Windows. For most desktop apps, you won’t notice.

Speed equivalence

That X1C6 is roughly equivalent to a mid-2017 ultrabook PC running Windows 10 directly.

In raw terms, it’s ~comparable to a mid-range Core i5/i7 desktop from 2012–2013 or a very fast Core 2 Quad era tower.
So if the Pi 4 under Wine feels like a Pentium II/III (400–800 MHz), the Carbon feels like a 3+ GHz quad-core Core i5/i7, i.e. many orders of magnitude faster.

Practical expectations

Apps: Office, browsers, Winamp, Photoshop CS6, Notepad++ → run just as smoothly as on Windows.
Games:
- Older DirectX 7–9 titles (e.g., Half-Life 2, Morrowind, Fallout 3) → fine, though GPU is the limit.
- DX10–11 stuff → mixed results; some will run, others struggle due to Intel iGPU + Wine driver layers.
- DX12 or very new AAA → mostly out of reach.

Bottom line

On a Pi, Wine feels like 1999–2002 PC speed.
On your X1C6, Wine feels like native 2017 ultrabook speed—basically what the hardware really is, with only minor slowdown.

Do you want me to map out specific games/apps against what you could realistically expect on the X1C6 under Wine (like I did for the Pi)?