Currently, it is not possible to make use of WebAssembly proposal/features that aren't enabled by default in components. This is because unlike wasm-tools validate which allows a --features CLI arguments to extend (or reduces) the set of Web Assembly proposals/features supported.
This prevents users from making components out of valid Wasm modules, for example ones that use the custom-page-sizes proposal which is otherwise supported by wasmtime and wasm-tools. As far as I can tell, nothing in theory prevents this proposal from being used in components so it's a shame that this is currently impossible when it could easily be supported.