The missing ones are HTTP OPEN/CLOSE to improve the sessions management and security audits.
From the very first line in the RFC[1]:
"The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems."
Which is why you need to send a header every time you make a request with authorization data.
Given that: no, stateful methods like OPEN/CLOSE would not fit at all with how HTTP is designed to work.