I disagree. x86 is totally stack oriented. 25% of their original registers are dedicated to working off the stack and it includes the ENTER/LEAVE instructions for facilitating those operations. Code would be totally tedious without them and the base+offset operations on memory. Seriously there are only 4 gp registers and 2 of those are generally used for indexed addressing and loop operations.
Maybe you could make some argument that x86 was stack oriented in 16-bit mode, although even there it's pretty tenuous to claim that by bp alone since there isn't anything particularly stack-dedicated about it outside of enter/leave. The fact that sp isn't directly addressable would be a stronger argument towards stack orientation. But because of enter/leave? You'd may as well say that the rep prefix instructions make it string oriented. At least those instructions weren't gradually performance degraded into uselessness like enter/leave or loop were.
I've done a fair amount of x86 coding (none of it 30 years ago mind you, don't know what your experience was) and personally I've never used ebp/rbp for anything dedicated to stack addressing, nor have I ever used enter/leave. Compilers are more or less the same - they could use ebp/rbp as a frame pointer but that's no different from using a frame pointer in other ISAs (and removed with ie -fomit-frame-pointer)