No, this is not guaranteed, each ML job will also look for specific fields with specific values on them, they are built to support data from integrations.
For example the Spike in Logon Events , if you check the documentation it mentioned that this job was built to support a couple of integration with data from Windows systems, it requires this data.
This job will also only look for events where the field event.category has the value authentication and event.outcome has the value success as described here, it also has the field winlog.event_data.LogonType as one of the influencers for the job as described here.
So I would not expect this to work with any other kind of data.
As mentioned in the previous posts, pre-built detection rules and ML jobs expected data from existing integrations.
With an Enterprise license you can also edit Elastic rules and change them to look at your custom indices, but the query needs to match, sometimes is way more easier and requires less work to simple create a custom rule.