Could you provide a example of a 'type=create' problem affecting VE? Is it used on main or user namespace in your wiki?

In the plwiki, we have no important inputbox with 'type=create' in the main nor user namespace, but there are inputboxes in help or project pages which create a new article (for ex. [[pl:Pomoc:Tworzenie nowych haseł#Niniejsza strona]]), and after clicking the button there is 'action=edit&preload=' in url.

Second, whenever we click on a red link in an article (the main), 'action=edit&redlink=1' displays. The default tab is 'Create source', not 'Create'. It's quite surprising for me and for the newbies, I believe.

Ah, I see a process problem with type=fulltext too

inputbox goes to search results, and search results show a red link, which the user would click on to start a new page. e.g.

https://en.wikipedia.org/wiki/Special:Search/this_article_doesnt_exist

I believe that some enhancement will be needed in the InputBox extension to support creating VE or SE articles.
https://www.mediawiki.org/wiki/Extension:InputBox

You can easily point InputBox to VE with a simple hook so that VE can change 'action' to 'veaction'. But that won't make VE magically support all the additional parameters which InputBox uses (e.g. preload, editintro, summary, minor, etc.)

I don't want to make inputbox suddenly magically different. It's about ordinary users (especially the new sort 'born' after VE deployment) who want to type a new article's name, click on button and voila, start creating their article in VE. In 2 steps, after 1 click, without experience like 'why the markups? oh, I'm switching to VE'. They'd be more likely to give up in this case.

Technically, you may change the default 'action' with 'veaction' or create a new parameter or sth else, it's up to you.

Did SET work affect this...?

In T54162#2590097, @Elitre wrote:

Did SET work affect this...?

Not yet; it will need further work.

This should become feasible after we implement T223793: On non-SET wikis (two edit tabs), links to new pages (red links) should open the user's preferred editor (last used). We can probably use a similar mechanism to intercept the targets of inputboxes.

Also, note that a useve=true inputbox parameter has been implemented in the meantime: T89341: Option to choose editor (traditional vs VisualEditor) in InputBox extension.